Supply chain management system

ABSTRACT

An illustrative method for managing a supply chain is performed by a supply chain management server. The method comprises receiving information related to operations of a first supplier. The first supplier is responsible for providing a first product that satisfies criteria of a buyer. The method further includes determining a risk value that indicates a risk level of disruption of the operations of the first supplier and flagging the first supplier within a database of potential suppliers in response to determining that the determined risk value is greater than a risk tolerance threshold. The method also comprises notifying the buyer that the first supplier has been flagged and providing a list of recommended suppliers to the buyer. The recommended suppliers are each capable of providing a respective second product to the buyer. Each of the respective second products satisfies the criteria of the buyer.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/978,680, filed May 14, 2018 (now U.S. Pat. No. 10,853,751), which isa continuation of U.S. patent application Ser. No. 14/738,594 (now U.S.Pat. No. 9,971,981), filed Jun. 12, 2015, which claims priority to andthe benefit of U.S. Provisional Patent Application No. 62/011,942, filedon Jun. 13, 2014, each of which are incorporated herein by reference intheir respective entireties.

FIELD

The present disclosure relates generally to the field of supply chainmanagement. More particularly, the present disclosure relates topredictive analytics for use in determining supply chain disruption,predictive analytics for use in matching buyers and suppliers, andcrowd-sourced user ratings.

BACKGROUND

The following description is provided to assist the understanding of thereader. None of the information provided or references cited is admittedto be prior art. Some manufacturers rely on products from suppliers intheir production. Manufacturers often employ regimented schedules thatare planned carefully. Thus, when a supplier fails to provide productsto a manufacturer, the manufacturer's product can be stalled, therebycosting the manufacturer time and money and potentially delayingshipments to its customers. Thus, a system that can predict when asupplier might fail to deliver its product may be helpful. Also, asystem that can help identify the best alternative supplier may behelpful.

SUMMARY

An illustrative method for managing a supply chain is performed by asupply chain management server. The method comprises receivinginformation related to operations of a first supplier. The firstsupplier is responsible for providing a first product that satisfiescriteria of a buyer. The method further includes determining a riskvalue that indicates a risk level of disruption of the operations of thefirst supplier and flagging the first supplier within a database ofpotential suppliers in response to determining that the determined riskvalue is greater than a risk tolerance threshold. The method alsocomprises notifying the buyer that the first supplier has been flaggedand providing a list of recommended suppliers to the buyer. Therecommended suppliers are each capable of providing a respective secondproduct to the buyer. Each of the respective second products satisfiesthe criteria of the buyer.

An illustrative system for managing a supply chain comprises acommunications transceiver, a memory and a processor. The communicationstransceiver is configured to communicate with a plurality of buyers anda plurality of suppliers. The memory is configured to store a databaseof information, a database of disruption event information, and adatabase of the plurality of suppliers. The information relates tooperations of a first supplier. The first supplier is responsible forproviding a first product that satisfies criteria of a buyer. Thedisruption event information comprises information indicating disruptionof the operations of the first supplier of the plurality of suppliers.The processor is operatively coupled to the communications transceiverand the memory. The processor is configured to receive the information,receive the disruption event information, and determine a risk valuethat indicates a risk level of disruption of the operations of the firstsupplier based on the disruption event information. The processor isfurther configured to flag the first supplier within the database of theplurality of suppliers in response to determining that the determinedrisk value is greater than a risk tolerance threshold, notify, via thecommunications transceiver, the buyer that the first supplier has beenflagged, and provide, via the communications transceiver, a list ofrecommended suppliers to the buyer. The recommended suppliers are eachcapable of providing a respective second product to the buyer. Each ofthe respective second products satisfies the criteria of the buyer.

An illustrative non-transitory computer-readable medium includescomputer-readable instructions that, upon execution by a processor,cause a device to perform operations. The operations include receivinginformation related to operations of a first supplier. The firstsupplier is responsible for providing a first product that satisfiescriteria of a buyer. The operations further include determining a riskvalue that indicates the risk of disruption of the operations of thefirst supplier and flagging the first supplier within a database ofpotential suppliers in response to determining that the determined riskvalue is greater than a risk tolerance threshold. The operations alsoinclude notifying the first supplier that the first supplier has beenflagged and providing a list of recommended suppliers to the buyer. Therecommended suppliers are each capable of providing a respective secondproduct to the buyer. Each of the respective second products satisfy thecriteria of the buyer.

The foregoing summary is illustrative only and is not intended to be inany way limiting. In addition to the illustrative aspects, embodiments,and features described above, further aspects, embodiments, and featureswill become apparent by reference to the following drawings and thedetailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a supply chain management system inaccordance with illustrative embodiments.

FIG. 2 is a block diagram illustrating an example of possiblerelationships between buyers and suppliers in accordance with anillustrative embodiment.

FIG. 3 is a flow chart of supply chain disruption risk subsystem inaccordance with an illustrative embodiment.

FIG. 4 is a flow chart of supply chain disruption risk determination inaccordance with an illustrative embodiment.

FIG. 5A is a flow diagram of a method of notification for identified SCDevent affected suppliers in accordance with an illustrative embodiment.

FIG. 5B is an illustration of a dashboard display in accordance with anillustrative embodiment.

FIG. 5C is an illustration of a user profile display in accordance withan illustrative embodiment.

FIG. 5D is an illustration of a company profile display in accordancewith an illustrative embodiment.

FIG. 5E is an illustration of a display of a company's financialinformation in accordance with an illustrative embodiment.

FIG. 6 is a flow diagram of a method for updating the determination thata supplier is at risk of being affected by an SCD event in accordancewith an illustrative embodiment.

FIG. 7 is a flow diagram of a buyer-supplier matching subsystem inaccordance with an illustrative embodiment.

FIG. 8A is a flow diagram of buyer-supplier matching in accordance withan illustrative embodiment.

FIG. 8B is a flow diagram of a method for notifying users of abuyer-supplier match in accordance with an illustrative embodiment.

FIG. 8C is a flow diagram of a method for improving recommendations inaccordance with an illustrative embodiment.

FIG. 8D is an illustration of a graphical representation ofrecommendations in accordance with an illustrative embodiment.

FIG. 9 is a flow diagram of a rating subsystem in accordance with anillustrative embodiment.

FIG. 10A is a flow diagram for calculating user scores in accordancewith an illustrative embodiment.

FIG. 10B is a flow diagram of a method of updating a user's score inaccordance with an illustrative embodiment.

FIG. 11 is a block diagram of a controller in accordance with anillustrative embodiment.

The foregoing and other features of the present disclosure will becomemore fully apparent from the following description and appended claims,taken in conjunction with the accompanying drawings. Understanding thatthese drawings depict only several embodiments in accordance with thedisclosure and are, therefore, not to be considered limiting of itsscope, the disclosure will be described with additional specificity anddetail through use of the accompanying drawings.

DETAILED DESCRIPTION

Detailed embodiments of the invention are disclosed herein. However, thedisclosed embodiments are merely exemplary and the concepts disclosedherein may be embodied in various and alternative forms. The figures arenot necessarily to scale, and some features may be exaggerated orminimized to show details of particular components. Therefore, specificstructural and functional details disclosed herein are not to beinterpreted as limiting, but merely as representative of the disclosedparticular embodiments with the understanding that these may varyaccording to other exemplary embodiments.

Each of the repositories and databases disclosed herein may beimplemented in database software such as MySQL, Oracle DB, and MicrosoftSQL Server, whether hosted locally, distributed over a network, orhosted on the cloud. The information stored in a repository or databasemay be obtained using one or more of the following: web crawlers; buyersand/or suppliers inputting the data into the repository or database; asystem administrator of the repository, database, subsystem, or thesystem manually inputting the data into the repository or database; anddirect communications from data sources. The repositories and databasesmay be updated periodically or continuously either automatically ormanually. Although various databases are described herein, one or moreof the various databases can be the same and/or include the same orsimilar information. That is, databases described herein that includethe same or similar information can be the same database.

In various contexts, such as in a manufacturing context, buyers andsuppliers have ongoing relationships. For instance, an automobilemanufacturer in the United States can buy bushings from a supplier inIndia. The automobile manufacturer and the supplier in India can have anongoing relationship in which the supplier in India sends bushings tothe automobile manufacturer on a regular basis, e.g., monthly. Theautomobile manufacturer can rely on the supply of bushings in itsmanufacturing plant for consistent production of automobiles. Thus, ifthe stream of bushings ceased, without notice, the automobilemanufacturer may have to shut down production until a new supply ofbushings, with the same or substantially similar properties (e.g., size,material, tolerances, etc.), can be established. Accordingly, theautomobile manufacturer in the United States can be affected by, forexample, an earthquake in India that interrupts the supply of bushingsby shutting down the supplier in India.

Using aspects of the present disclosure, the production of theautomobile manufacturer in the United States can continue, even when themanufacturer's primary supplier of bushings from India is unexpectedlyshut down. In some embodiments, a platform is provided in which therelationship between the automobile manufacturer and the supplier inIndia is monitored. Further, the status of the automobile manufacturerand the supplier can be monitored as well as events that may affect themanufacturer and supplier. For example, news events can be monitored,and news of an earthquake in an area in which the Indian supplier islocated can be automatically detected by a system. The system can thenidentify one or more other suppliers of bushings used by the automobilemanufacturer in the United States. The system can notify the automobilemanufacturer of the disruption (or potential disruption) of its supplyof bushings and provide recommended alternative suppliers. Thealternative suppliers can be ranked and/or scored to assist theautomobile manufacturer in choosing the most appropriate alternativesupplier.

Thus, in such an example, the automobile manufacturer can quicklyreplace its supply of bushings such that production of automobiles cancontinue unhindered. In some embodiments, the system can respond todisruptions (or potential disruptions) in a supply chain and findsuitable alternatives to repair any disruption in the supply chain.Further, the system creates efficiencies in the supply chain. Forexample, alternative suppliers can be identified that provide the same(or substantially similar) products at a lower cost than a currentsupplier. In another example, suppliers with a higher quality or a moresuitable product for a buyer's needs can be identified. Thus, instead ofthe buyer (or the buyer's supply chain system) recognizing a supplychain problem when either notified by the supplier or when the buyer'sshipment does not arrive on time, aspects of the present disclosureidentify the supply chain problem much earlier in the process andprovide recommendations for alternative suppliers, thereby minimizingthe risk that a buyer will not receive an ordered product on time and/orreducing the amount of time the buyer will have to wait to receive theordered product.

Another efficiency of some embodiments is the identification of qualitysuppliers and/or a ranking system for suppliers. Various aspects of asupplier can be identified and used to score and/or rank the supplier.Some example aspects include financial information, manufacturingcapabilities, and customer satisfaction/experience. The scores and/orrankings can be used to determine the best candidates for the supply ofa particular product for a particular buyer. In some embodiments, thescoring and/or ranking can be based on the buyer's particularneeds/wants. Thus, a system of the present disclosure can identify for abuyer the best-suited suppliers for a buyer's particular situation.Instead of the buyer receiving and searching through a list of suppliersthat are capable of providing the buyer's part, piece, material, etc.and the buyer sorting through and determining which suppliers are bestsuited for the buyer, the system can automatically and efficientlyprovide the best-suited suppliers.

Some embodiments of the present disclosure provide a supply chainmanagement system that can match buyers and suppliers that shouldconduct business together. The matched buyers and suppliers may havesimilar needs and offerings. The supply chain management system performspredictive analytics, thereby promoting more efficient use ofmarketplace dynamics and streamlining the interaction between buyers andsuppliers. For example, buyers can leverage a system that matches buyersand suppliers to receive suggestions for whom they should work with.These suggestions could be received on a one-time or on-going basis.Similarly, suppliers can leverage buyer-supplier matching subsystem 115to more efficiently target their business development activities.

FIG. 1 is a block diagram of a supply chain management system inaccordance with illustrative embodiments. According to other exemplaryembodiments, additional, fewer, and/or different elements may be used.System 100 includes a supply chain management (SCM) system 105, aplurality of user devices 130, and a network 125. The supply chainmanagement system 105 has a supply chain disruption (SCD) risk subsystem110, a buyer-supplier matching subsystem 115, and a rating subsystem120. According to other exemplary embodiments, SCM system 105 caninclude additional subsystems not represented in FIG. 1.

Supply chain management system 105 can include one or more computers,servers, logic devices, specialty computing devices, etc. Subsystems ofthe supply chain management system 105 can themselves be run on separatecomputing devices or can be run on the same computing device. The supplychain management system 105 is communicatively connected to a pluralityof user devices 130 through network 125. In some embodiments, network125 can be a local connection, such as via a cable. In some embodiments,network 125 can include a communications network such as a local areanetwork (LAN), a wide area network (WAN), a virtual private network(VPN), a cellular network, and/or the Internet. In some embodiments,network 125 can include wired and/or wireless connections. According toother exemplary embodiments, network 125 can include any suitablecommunications network. Each user device 130 can be a device of a buyerof products and/or a supplier of products. In some embodiments, userdevices 130 can communicate with one another directly through network125. According to other exemplary embodiments, user devices 130 cancommunicate with one another via SCM system 105.

FIG. 2 is a block diagram illustrating an example of possiblerelationships between buyers and suppliers in accordance with anillustrative embodiment. According to other exemplary embodiments,additional, fewer, and/or different relationships and/or entities mayexist. FIG. 2 illustrates buyer 201 and buyer 202 and supplier 251,supplier 252, and supplier 253. FIG. 2 is meant to be illustrative only,and not meant to be limiting as to the number or configuration of buyersand suppliers. For example, any suitable number of buyers or supplierscan exist. In some embodiments, one entity can be a buyer and asupplier. In some embodiments, one entity can include multiple buyersand/or suppliers. In FIG. 2, lines between the buyers and suppliers canbe representative of a relationship.

As illustrated in FIG. 2, in one example, buyer 201 can have arelationship with one supplier, supplier 251. In another example, buyer202 can have relationships with multiple suppliers, supplier 251,supplier 252, and supplier 253. Examples of relationships can becontractual relationships, prospective relationships, priorrelationships, etc. Contractual relationships can include, for example,an agreement for a buyer to purchase a certain quantity of parts, amemorandum of understanding, etc.

FIG. 3 is a flow chart of a supply chain disruption risk subsystem inaccordance with an illustrative embodiment. According to other exemplaryembodiments, additional, fewer, and/or different elements may be used.Further, the use of arrows is not meant to be limiting with respect tothe order or flow of operations. Supply chain disruption (SCD) risksubsystem 110 can include operations such as SCD risk determination 305,notification 310, risk update 315, and recommendation 320.

In most instances, it can be advantageous for buyers to be able toidentify high-risk suppliers as soon as possible after a supply chaindisruption event occurs. A supply chain management system incorporatingSCD risk subsystem 110 can allow buyers to be more proactive byproviding buyers with detailed supply chain disruption information inreal time or shortly after an SCD event occurs. Buyers are able toleverage the identification of high-risk suppliers to create plans tomitigate costly SCD events from negatively impacting their business. Insome embodiments, suppliers can be notified of an SCD event impactinganother supplier, such as a competitor. In such embodiments, a suppliercan take advantage of a competitor who is unable to supply its customerswith a product by replacing the competitor (at least temporarily) in thesupply chain.

FIG. 4 is a flow chart showing operations for supply chain disruptionrisk determination in accordance with an illustrative embodiment.According to other exemplary embodiments, additional, fewer, and/ordifferent elements may be used. Further, the use of arrows is not meantto be limiting with respect to the order or flow of operations. SCD riskdetermination 305 includes gathering risk-related data 405, predictingsupply chain disruption locations 410, predicting location-specificsupply chain disruption affected suppliers 415, predictingnon-location-specific supply chain disruption affected suppliers 420,and receiving a request for an updated prediction 425.

Gathering risk-related data 405 can include receiving informationrelated to a supply chain disruption. Such information can include, forexample, an indication that a tsunami impacted a region or city, anindication that there was a fire at a warehouse of a supplier, anindication that a supplier has filed for bankruptcy, etc. Suchinformation can be gathered from one or more sources, such as users ofthe system (e.g., via user devices 130); the Internet; electronic dataexchanges using either non-standardized formats or standardized formats(e.g., such as those provided by Electronic Data Interchange (EDI));social media such as Twitter, Facebook, LinkedIn, etc.; weather sourcessuch as weather.com; news sources, newspapers, and news websites such asBloomberg, Fox News, CNN, CNBC, The Economist, Wall Street Journal, TheFinancial Times, NPR News, Huffington Post, BBC News, Reuters, The NewYork Times, The Guardian, Mail Online, USA Today, The Washington Post,ABC News, the Los Angeles Times, etc.; blogs such as blogs.com andWordPress.com; search portals such as Google, Bing, Yahoo, etc.;customer data; governments; universities; third parties; etc.

The risk-related data can be gathered and/or received using one or moremethods, such as web crawlers; buyers and/or suppliers inputting datainto system 100; a system administrator (or other user) inputting datamanually into SCD risk subsystem 110; direct communications from datasources; etc. The risk-related data gathered can be stored in one ormore memory devices, such as databases, repositories, servers, etc. FIG.4 shows the risk-related data stored in a supply chain disruption datadatabase. Any suitable method of storing the risk-related data can beused. For example, in some embodiments, pieces of data can be storedtemporarily based on the type of information each piece of datacontains. For example, a piece of data related to a snowstorm can bestored for a predetermined amount of time depending upon the severity ofthe snowstorm. In another example, the piece of data related to thesnowstorm can be stored until an indication is received that thesnowstorm is over or is resolved (e.g., roads are plowed).

Any suitable method can be used to read and/or load information intodatabases, repositories, etc. In some embodiments, an extraction,transformation, and load (ETL) technique is used to load data gatheredfor SCD event determination into a repository. Other methods now knownor later developed for loading data into a repository may also be used.For example, the data in a repository may be categorized usingcategories such as event types, locations, time, source, etc. The abovedata categories are merely illustrative. Other methods of categorizingdata related to SCD and now known or later developed may also be used.Data stored on a database may be used for predicting suppliers andsupplier locations with high risks of SCD events.

In some embodiments, SCD risk subsystem 110 can determine the relevancyof the data gathered for SCD risk determination 110 using a repositoryof SCD keywords, such as the supply chain disruption keyword databaseshown in FIG. 4. In some embodiments, the repository of SCD keywords maycontain one or more of categories of keywords such as finance; mergersand/or acquisitions (M&A); weather; government; and operations. Thefinance category of keywords can include keywords such as financialdistress; bankruptcy; bankrupt; insolvency; closing; closing doors;dissolving; liquidity; cash flow; paying suppliers on time; creditcrisis; currency volatility; FX exchange issue; financial crisis; etc.The M&A category of keywords can include keywords such as merger;acquisition; M&A; “company X buying company X” (where “company X” can beone or more names of suppliers); buyout; leveraged buyout; LBO;shareholder activist; hostile takeover; board shakeup; CEO departure;CEO firing; chairman departing; CEO appointment; etc. The weathercategory of keywords can include keywords such as flood; storm; tsunami;tornado; earthquake; snowstorm; avalanche; dust storm; hail storm; icestorm; road closures; fire; forest fire; volcano; adverse weather; etc.The government category of keywords can contain keywords such astariffs; economic unrest; geological; war; invasion; political unrest;civil war; conflict; battle; etc. The operations category of keywordscan include keywords such as plant strike; labor issues; labor unrest;downtime; closed; supply chain disruption; disruption; logistics issues;supply chain break; IT outage; information systems outage; power outage;quality issue; recall; quality concern; plant fire; explosion; factorycollapse; poor working conditions; minimum wage increase; etc. Theabove-listed keywords and categories of keywords are merelyillustrative. Other keywords and categories of keywords now known orlater developed as being related to SCD, or the likelihood of SCDoccurring, may be used in connection with SCD risk subsystem 110.

In some embodiments, categories of keywords and/or keywords can havedifferent weights. That is, some categories of keywords and/or keywordscan require greater severity and/or certainty than others to determinethat an SCD event of the category of keywords and/or keywords willaffect a supplier. For example, a warehouse fire can be weighted higherthan geopolitical events. In such an example, fewer sources reporting afire at a supplier's warehouse can be required to meet a riskdetermination threshold than sources reporting that a new politicalparty was elected in a supplier's region. That is, it is more likelythat a warehouse fire will affect a supplier's ability to satisfy ordersthan it is that a political regime change will affect a supplier'sability to satisfy orders. As mentioned, keywords within a particularcategory can have different weights. For example, a war or bombings in aregion of a supplier can be weighted higher than political regime changeeven though war, bombings, and regime change may be under a geopoliticaland/or government category.

In some embodiments, keywords can be classified into categories relatedto the degree or manner of impact to suppliers. For example, thekeywords could be categorized into supplier-specific, supplierlocation-specific, and location-specific keywords. A supplier-specificcategory can include events that affect the supplier as a whole (e.g.,all of the factories of a supplier are affected). For example,“bankruptcy” can be a keyword that affects a supplier as a whole. Asupplier location-specific category can include events that affect asupplier at a particular location. For example, “fire” or “warehousefire” can be keywords that affect a particular location of a supplier. Alocation-specific category can include events that affect all (or most)suppliers at a particular location. For example, “tsunami” can be akeyword that affects a particular location.

In some embodiments, risk-related data gathered in operation 405 can bereceived from the supplier and/or a distributor. For example, in someembodiments, data can be received related to a particular shipment.Trucks used to transport products can be equipped with a locationdetection device (such as a GPS sensor) and a communications transceiver(such as WiFi, cellular, etc.). The devices on the trucks can be used tocommunicate information to SCM system 105. Thus, trucks can transmittheir location (or any other relevant information such as speed, status,malfunction, tire pressure, etc.) to SCM system 105 and the trucks'location can be received in operation 405. For example, a trucktransporting products from a supplier to a buyer can be stuck in an areain which the roads were destroyed by a landslide. The devices on thetruck can be used to transmit to the SCM system 105 that the truck isbehind on its expected route and schedule. Such information can be usedto determine that the supplier is affected by an SCD event (discussed ingreater detail below). Thus, the buyer (or SCM system 105) can monitor asupply chain in real time. Such information can be used to assesspotential supply chain disruption events, react quickly and efficientlyto supply chain disruption events, and monitor supply chain mappingflows (e.g., allow supply chain visibility).

In some embodiments, the risk-related data gathered in operation 405 canbe received by reporting systems of the supplier. Suppliers can usecomputer systems (including programmable logic computers (PLCs),supervisory control and data acquisition (SCADA) systems, human-machineinterface (HMI) systems, etc.) to control and/or automate manufacturingprocesses. Such computer systems can receive information from sensorsand produce information (such as which step a manufacturingbatch-process plant is in) indicating the status of the supplier'smanufacturing process. Such computer systems can be used to transmitstatus information to SCM system 105. For example, if a manufacturingplant is shut down, behind schedule, etc., an indication of such can betransmitted to SCM system 105 and can be received in operation 405. Anysuitable or useful information can be received in operation 405, such asproduct quality, product amount, inventory amount, the number ofproducts currently being worked on, raw materials available, etc. Insome instances, the supplier can provide reports containing suchinformation directly to the supplier's buyers. In other instances, thesupplier can provide a report to SCM system 105, and the SCM system 105can distribute the relevant information to the supplier's buyers.Further, the SCM system 105 can use the information to determine whetherthe supplier is affected by an SCD event. For example, if a productpurity level is below a buyer's threshold purity level, the SCM system105 can determine that the supplier will not be able to deliver theproduct with the proper purity to the buyer on time and, therefore, isaffected by an SCD event.

As shown in FIG. 4, in some embodiments, predicting SCD locations 410,predicting location-specific SCD affected suppliers 415, and predictingnon-location-specific SCD affected suppliers 420 can follow gatheringrisk-related data 405. Predicting SCD locations 410, predictinglocation-specific SCD affected suppliers 415, and predictingnon-location-specific SCD affected suppliers 420 can use therisk-related data gathered in operation 405. As discussed above,predicting SCD locations 410 can determine geographic locations that areor may be affected by a supply chain disruption event. As shown in FIG.4, predicting location-specific SCD affected suppliers 415 can use thegeographic locations identified by predicting SCD locations 410.

In operation 415, SCD affected suppliers can be identified usingidentified SCD locations by identifying suppliers who have facilities inthe identified SCD locations. The facilities of the suppliers can bestored in the supplier location database as shown in FIG. 4. Forexample, it may be determined that a city in South Africa is inpolitical turmoil and operations of the city have been shut down. Suchinformation can be identified in operation 405, and the city in SouthAfrica may be identified in operation 410 as having a supply chaindisruption event. Operation 415 can cross-reference the city in SouthAfrica with operation locations of suppliers and identify that SupplierA has a manufacturing plant in the city of South Africa that is (or maybe) affected by the political turmoil.

In operation 420, SCD affected suppliers can be identified without usingthe identified SCD locations. For example, Supplier B may have announcedthat it will discontinue production of a microprocessor. Suchinformation can be identified in operation 405, and, based on theinformation, Supplier B can be identified as being a supply-chaindisruption affected supplier in operation 415, at least with regard tosupplying the microprocessor. Accordingly, Supplier B can be identifiedin operation 415 without regard to an identified SCD location that wasdetermined in operation 410.

Any suitable method of predicting a location that has a supply chaindisruption event (e.g., operation 410) or predicting supply chaindisrupted suppliers (e.g., operations 415 and 420) can be used. In anillustrative embodiment, if more than a threshold number of sources areidentified (e.g., in operation 405) within a certain time period thatreport that a location has an SCD event, then it can be predicted thatthe location has sufficient risk of the SCD event. In some embodiments,the certain time period can be constant for all SCD events. According toother exemplary embodiments, the certain time period can vary dependingupon the SCD event. For example, an SCD event of a landslide can have afirst time period (e.g., twenty-four hours) and an SCD event ofpolitical turmoil can have a second time period (e.g., one week).

In some embodiments, the threshold number of sources can be constant forall sources that are indicating the SCD event. According to otherexemplary embodiments, the threshold number of sources can be dependenton the reliability of the sources. For example, the threshold can berelatively low (e.g., three sources) when the reporting sources arereliable (e.g., the Associated Press, a government agency, etc.), butthe threshold can be relatively high (e.g., five hundred) when thereporting sources are unreliable (e.g., Twitter, blogs, etc.). In suchan example, each source can be weighted differently depending uponreliability, and the threshold can be a threshold score. For example,the threshold score can be ten. The threshold score can be satisfiedwhen a news source weighted with a score of four, a government sourceweighted with a score of five, and one hundred Twitter sources eachweighed with a score of 0.02 all report an SCD event. The weightedscores can be summed, and because the weighted scores add to greaterthan ten (the threshold score), the SCD event can be predicted withsufficient risk tolerance.

In some embodiments, a source's weight can be time-dependent. In suchembodiments, the source's weight can include a time decay element. Forexample, the weight given to a source's report of an SCD event can be

S·e^(t) ^(s) ^(−t) ^(c)

where S is the score given to the source for the SCD event (which can beweighted, as discussed above), t_(s) is the time that the sourcereported the SCD event, and t_(c) is the current time. The weightedscores of various sources can be summed and, if the sum of the weightedscores is above a threshold, the system can determine that the SCD eventoccurred. Thus, the older that a report is, the smaller the impact thereport will have on determining that the SCD event occurred.Accordingly, if enough sources report the SCD event within a shortenough time period, the system can determine that the SCD eventoccurred.

In some embodiments, SCD risk determination 305 can include monitoringdetected SCD events. For example, SCD risk determination 305 candetermine that a snowstorm in Detroit, Mich., may affect a supplier inDetroit. SCD risk determination 305 can use the methods described above,or any other suitable method, to monitor the status of the snowstorm todetermine when the risk of the SCD event is over. For example, thesnowstorm may be less severe than predicted, and SCD risk determination305 can determine that the supplier is not at risk of being affected. Inanother example, the snowstorm may impact the city of Detroit, and SCDrisk determination 305 can determine when the snowstorm effects nolonger affect suppliers. In such an example, SCD risk determination 305can include determining that roads in Detroit are sufficiently plowedand that power has been restored to the city.

In some embodiments, different suppliers can have differently weightedSCD events. That is, one or more of the various weights described abovecan be supplier-dependent. For example, a trucking company in Chicago,Ill., may have snowstorms weighted as a higher risk potential than asoftware company located in Chicago. The trucking company can be moresusceptible to inclement weather than the software company.

In some embodiments, one or more score weights can be adjusted. In someembodiments, the score weights can be adjusted manually. The scoreweights can be adjusted by a system administrator and/or by thesuppliers. For example, if a supplier knows that the supplier is moresusceptible to cold weather than it is to a warehouse fire, the suppliercan adjust the weight of a cold weather SCD event higher than awarehouse fire SCD event. In some embodiments, one or more weights canbe adjusted automatically. For example, the system can monitor pastpredicted (or not predicted) SCD events and whether the identifiedsupplier was actually affected by the SCD events. For example, ifsuppliers are flagged as at risk of a governmental coup, but thesuppliers are still able to meet their orders, the weight ofgovernmental coups can be reduced. In another example, if a supplier hasone or more warehouse fires, but is still able to fulfill its orders,the weight of warehouse fires can be reduced. In such an example, theweight of warehouse fires can be reduced for that supplier. Thus, byadjusting weights, the accuracy of predicting whether a supplier isaffected by an SCD event can be increased. Any suitable “learning”algorithm may be used.

In some embodiments, SCD risk determination 305 can predict an SCD eventfirst order effect, second order effect, third order effect, etc. Afirst order effect can be an effect on a supplier that is causeddirectly by the SCD event. For example, a warehouse fire can cause afirst order effect to a supplier that stores product in the warehouse. Asecond order effect can be an effect on a supplier that is caused byanother supplier that is directly affected by the SCD event. Forexample, the warehouse fire can destroy plastic pellets of a firstsupplier that a second supplier uses in its computer monitor that itsupplies to customers. Thus, although the second supplier did notexperience a warehouse fire, its supply of plastic may be affected,which may affect the second supplier's ability to fulfill its customerorders. In some embodiments, the second supplier can be identified as(potentially) impacted by the warehouse fire SCD event in SCD riskdetermination 305.

In some embodiments, second order (or third order, etc.) effects can bedetermined by identifying customers of first order (or second order,etc.) affected suppliers who themselves are suppliers. In someembodiments, second order (or third order, etc.) effects can bedetermined by proximity to SCD events. For example, a tsunami can hitJapan, which can affect exports from Japan. A Chinese supplier can relyon imports from Japan for the product that it supplies. Thus, SCD riskdetermination 305 can determine that the Chinese supplier is at risk ofbeing affected by the tsunami SCD event based on its proximity to thetsunami-affected area (e.g., Japan). For example, the weight given topredicted first order SCD locations in computing possible second orderSCD events can be

e^(−D)

where D is the distance between the first order SCD location and thesecond order SCD location. In another example, the weight given topredicted first order SCD locations in computing possible second orderSCD events can be

$\frac{1}{D}$

where D is the distance between the first order SCD location and thesecond order SCD location. In some embodiments, such weights can also beused to determine first order SCD event affects. For example, distancefrom an SCD event can be relevant to some weather SCD events, a nuclearreactor meltdown, a volcano explosion, etc.

In some embodiments, one or more negative scores can be used todetermine whether an SCD event is still affecting suppliers. Forexample, a scoring system as described above can be used to determinethat a supplier is (potentially) affected by an SCD event. Negativescores can be added to (or positive scores can be subtracted from) thescore used to determine that the supplier is affected by the SCD affect.The negative scores can include sources that indicate that the SCD eventhas been resolved, has had less of an impact than expected, etc. Forexample, sources can indicate that a tsunami impacted Japan and SCD riskdetermination 305 can determine (as described above) that a firstsupplier is affected by the tsunami because the first supplier islocated in Japan. After a while, sources may start to indicate that thetsunami impact on Japan is resolved (e.g., power is restored, roads arecleared, businesses are open, etc.). Such sources can be used todetermine negative scores that can be added to the score that indicatedthat Japan is affected by an SCD event. When enough negative scores areadded to the score that indicated that Japan is affected by the SCDevent, the resultant score can be below the threshold for determiningthat Japan is affected by the SCD event, and the system can determinethat Japan is no longer affected by the tsunami. The negative scoresources can be any suitable source, for example, news sources,governments, etc. For example, other suppliers can indicate that theyare no longer affected by the SCD event. Using the example above, whenenough of the other suppliers indicate that they are no longer affectedby the tsunami and are fulfilling their orders, the system can determinethat Japan is no longer affected by the tsunami and, thus, that thefirst supplier is no longer affected by the tsunami.

As shown in FIG. 4, operations 405, 410, 415, and 420 can be runcontinuously. Also as shown in FIG. 4, in some embodiments, operations405, 410, 415, and 420 can be initiated by receiving a request for anupdated prediction 425. The requested for an updated prediction can bereceived by any suitable source such as a user or a systemadministrator. For example, a supplier who has been determined to be atrisk of being affected by an SCD event may dispute the determination andmay request that the determination is updated. For example, the suppliermay have been identified as being in a town that was demolished by atornado. However, if the supplier's warehouse was unaffected, thesupplier can request an updated determination. In such an instance, theinformation regarding the warehouse still standing can be used whendetermining whether the supplier is at risk of being affected by the SCDevent.

In some embodiments, SCD risk determination 305 can include a supplychain visibility function that can allow a buyer to view informationrelated to a product throughout several tiers of production or severaltiers of the supply chain. For example, many products purchased bybuyers are not produced entirely by one supplier. That is, the supplieritself often is a buyer of products that the supplier uses duringmanufacturing. In some instances, the supplier can have otherrelationships that can affect a supply chain. For example, a suppliermay manufacturer a product and contract a third party to store ortransport the product. The supply chain visibility function can allow abuyer (or SCM system 105) to evaluate a supplier, the supplier'ssupplier, etc. Any suitable number of tiers can be monitored. Forexample, one, two, three, five, ten, etc. tiers can be monitored.

In an example, an automotive manufacturer can purchase half shafts fromSupplier A. Supplier A can purchase rubber boots for the half shaftsfrom Supplier B. Supplier B can purchase rubber for its rubber bootsfrom Supplier C. In some embodiments, gather risk-related data 405 canbe performed for each of Supplier A, Supplier B, and Supplier C.Relevant information can be provided to the automotive manufacturer toallow the automotive manufacturer to evaluate the half shafts purchasedfrom Supplier A. For example, SCM system 105 can determine that SupplierC often produces rubber that is lower quality than required for SupplierB. Thus, the automotive manufacturer or SCD risk subsystem 110 can usesuch information to determine a risk value that the half shafts orderedfrom Supplier A will be delivered on time. For example, the risk valuemay increase because the rubber boots received by Supplier A fromSupplier B have a greater risk of being defective, thereby delaying thedelivery of the half shafts to the automotive manufacturer from SupplierA.

Using the example above, SCD risk subsystem 110 can be used to determinethat the manufacturing plant of Supplier B was engulfed in a wildfireand, therefore, is at risk of being affected by an SCD event. Themanufacturing plant of Supplier B can be the manufacturing plant inwhich Supplier B manufactures the rubber boots that Supplier A uses inits half shafts provided to the automotive manufacturer. In someembodiments, such information can be presented to the automotivemanufacturer to alert them of the risk posed to the supply of halfshafts. In some embodiments, such information can be used to determine arisk that the Supplier A will be affected by the SCD event (e.g., thewildfire).

Thus, the supply chain visibility function can provide buyers (andsuppliers) with information that has traditionally been too cumbersome,difficult, and cost prohibitive to obtain. By using system 100, supplychain related information is gathered and analyzed efficiently by asingle system, such as SCM system 105. That is, by using a system suchas SCM system 105 that gathers information about various buyers andsuppliers, the information can be provided to users (e.g., buyers orsuppliers) without the users tracking down the information themselves.In some instances, the information can be routinely or automaticallyupdated. In some instances, the information can be information that isalready gathered by the SCM system 105 and special efforts may not needto be made by suppliers to provide the relevant information to SCMsystem 105.

In some instances, efficiencies can be created by crowd-sourcinginformation. Obtaining information into a system such as SCM system 105that can be quickly updated and maintained and distributing theinformation to multiple users of the system is more efficient andcheaper than users gathering and analyzing their own data. In someinstances, such a system can gather information that is not available toindividual users (buyers or suppliers). For example, if the automotivemanufacturer in the example above was interested in financialinformation of the rubber supplier Supplier C, the automotivemanufacturer may have a difficult time obtaining Supplier C's financialinformation. Supplier C may not be comfortable sharing such informationwith a company with which it has no direct relationship. However,Supplier C may feel comfortable sharing such information with a trustedsystem, such as SCM system 105.

In some embodiments, a buyer can request to view a supply chain. Forexample, a buyer can request to view three tiers of a particularproduct's supply chain. In such an example, the buyer can input into SCMsystem 105 identification information for the product (such as a serialnumber, part number, etc.). The first tier supplier (e.g., the supplierthat received the buyer's order) can input into SCM system 105 allsecond tier suppliers to the first tier supplier for the product. Thesecond tier supplier can include suppliers for parts that the first tiersupplier uses to manufacture the product, a supplier that the first tiersupplier gets the product from, a storage facility the product isstored, transportation processing locations such as docks, ports, andwarehouses, for the product, etc. The same or similar information canthen be gathered of the third tier suppliers from the second tiersuppliers. Thus, the buyer of the product (or SCM system 105) can viewthe locations of first, second, third, etc. tier suppliers to evaluate arisk that the product will not arrive to the buyer on time. For example,if a large portion of the first, second, and/or third tier suppliers arewithin a small area, the buyer may wish to find an alternative or backupsource for the part in the event a localized SCD event occurs, such as atsunami.

The supply chain visibility function can allow a buyer, supplier, or SCMsystem 105 to monitor a supply chain in real time. Thus, if, forexample, a typhoon hits Taiwan, the suppliers in a supply chain (e.g.,not just the suppliers to the buyer, but the suppliers' suppliers, etc.)affected by the typhoon (or potentially affected) can be quicklyidentified and the appropriate notifications can be sent to those whomay be affected. By quickly identifying risks such as a failure in thesupply chain, appropriate actions can be taken to minimize or eliminateany impact on a buyer (or supplier). For example, recommendedreplacements for affected suppliers can be identified. The recommendedreplacements can be contacted and arrangements can be made such that abuyer can still receive an order on time, or the time the buyer mustwait until the products are received can be minimized.

In some embodiments, SCD risk subsystem 110 can include notification ofsuppliers identified in SCD risk determination 305. FIG. 5A is a flowdiagram of a method of notification for identified SCD event affectedsuppliers in accordance with an illustrative embodiment. According toother exemplary embodiments, additional, fewer, and/or differentelements may be used. Also, the use of arrows in the flow diagram is notmeant to be limiting with respect to the order of operations.Notification 310 includes flagging a supplier 510, notifying potentialbuyers 515, identifying current buyers to notify 520, notifying currentbuyers 525, and notifying the supplier 530.

In some embodiments, a database or list can be maintained of suppliers.The database can include information such as the supplier's name,location(s), product(s), etc. The database can further include whetherthe suppliers are affected by an SCD event. In some embodiments, if itis determined in SCD risk determination 305 that a supplier is(potentially) affected by an SCD event, the database of suppliers isupdated to indicate that the supplier is (potentially) affected by theSCD event. In such embodiments, flagging suppliers 510 can includeupdating the database. In other embodiments, any suitable method can beused to flag suppliers to indicate that the suppliers are (potentially)affected by an SCD event.

In some embodiments, notification 310 can include notifying potentialbuyers 515. Notify potential buyers 515 can include, for example,displaying an icon on a screen indicating that a supplier is at risk ofbeing affected by an SCD event. For example, if a potential buyersearches a database for suppliers of bottled water, a list can bedisplayed indicating suppliers satisfying the potential buyer's searchcriteria. In the list, if a supplier is at risk of being affected by anSCD event, an icon can be displayed next to the name (or in the same rowor column) of the supplier. In other embodiments, the color of the textof the supplier's name can be indicative of the risk that the supplieris affected by the SCD event. Any suitable method of indicating that asupplier is at risk of being affected by an SCD event can be used. Insome embodiments, a supplier's profile page can indicate whether thesupplier is at risk of being affected by an SCD event.

In some embodiments, notification 310 can include identifying currentbuyers to notify 520. In some embodiments, “current buyers” can includeany entity that has a relationship with a supplier that has beenidentified as being at risk of being affected by an SCD event, or anysubset thereof. For example, “current buyers” can include buyers thathave open orders with the supplier, buyers who previously purchased fromthe supplier, buyers that have initiated a relationship with thesupplier but have not yet purchased from the supplier (e.g., amemorandum of understanding has been agreed to), buyers that haverecently visited the supplier's profile page, etc.

Identifying current buyers to notify of a supplier's risk of beingaffected by an SCD event can be performed using any suitable method. Forexample, a list of previous purchasers can be maintained for eachsupplier. In another example, a database, list, repository, etc. can bemaintained that keeps track of buyer-supplier associations, such as thebuyer-supplier association database shown in FIG. 5A. Such a databasecan include information gathered from platform users (e.g., buyers whosupply a list of current suppliers or suppliers who provide a list ofcurrent buyers); pending buyer-supplier transactions; a history of abuyer who rated a supplier; a history of a supplier who rated a buyer; abuyer-supplier interaction history (e.g., via messages, emails,complaints); a buyer-supplier transaction history; EDI; consultants;etc. Such a database can include information gathered from buyers;suppliers; buyers' websites; suppliers' websites; electronic dataexchanges using either non-standardized formats or standardized formats(e.g., electronic data interchange (EDI)); business intelligenceproviders (e.g., Covisint Corp.); industry associations; consultants;news organizations; governments; etc.

In some embodiments, all identified current buyers are notified of asupplier being at risk of being affected by an SCD event. According toother exemplary embodiments, only some of the current buyers are sonotified. For example, identified current buyers can have a weightedscore of their relationship to the supplier that is at risk of beingaffected by the SCD event. The weighted score can be based on thepotential of the buyer to be affected if the supplier fails to fulfillorders. In some embodiments, a buyer is notified if the buyer's score isabove a threshold. According to other exemplary embodiments, the type ofnotification can be dependent on the buyer's score. For example, a buyerwith a score of between zero and ten may not be notified; a buyer with ascore of between ten and twenty may be notified via email of a risk thatthe supplier may not fulfill orders; a buyer with a score of betweentwenty and thirty may be notified via email and short message service(SMS) text message; a buyer with a score of between thirty and forty maybe notified via email, SMS text message, and a phone call; etc. In someembodiments, the content of the notification can be modified based onthe buyer's score. The modified content can include the type of languageused (e.g., urgency), the amount of information included, options forfollowing up on the notification, etc.

A buyer's score can be determined based on the relationship that thebuyer has with the supplier. Various data points may have differingweights. For example, a confirmed outstanding purchase order can beweighted higher than a confirmed past purchase order. Additionally, thediffering weights can be time dependent, as described above, such thatmore recent data points are weighted heavier. In some embodiments, asdescribed above, the weights given to various data points can be alteredto provide a more accurate identification of buyers who are to benotified. In some embodiments, the buyer's score can be based on theimportance of the supplier's product to the buyer. For example, a buyerwho receives bottled drinking water from a supplier (where the bottleddrinking water can be easily obtained from another source) can have alower score than a buyer who receives a customized, critical componentof the buyer's product (e.g., an engine, a microprocessor, a display,etc.) from the supplier.

In some embodiments, notification 310 can include notifying currentbuyers 525. The buyers identified in operation 520 can be notified ofthe supplier's risk of being affected by an SCD event. Any suitablemethod of notifying buyers can be used. For example, buyers can benotified by displaying an alert on the buyer's dashboard, home page,etc.; displaying an alert on the supplier's information page, profilepage, etc.; emailing the buyer; calling the buyer; sending the buyer afax; sending the buyer an SMS text message; displaying an indication ona geographical information system (GIS) display; sending the buyer anin-platform message; sending the buyer a message via social media; etc.

In some embodiments, notification 310 can include notifying the supplier530. Notifying the supplier can include indicating to the supplier thatthe supplier has been flagged as being at risk of being affected by anSCD event. Any suitable method of notifying the supplier can be used.For example, the supplier can be notified by displaying an alert on thesupplier's dashboard, home page, etc.; displaying an alert on thesupplier's information page, profile page, etc.; emailing the supplier;calling the supplier; sending the supplier a fax; sending the supplieran SMS text message; displaying an indication on a geographicalinformation system (GIS) display; sending the supplier an in-platformmessage; sending the supplier a message via social media; etc.

FIG. 5B is an illustration of a dashboard display in accordance with anillustrative embodiment. According to other exemplary embodiments,additional, fewer, and/or different elements may be used. Also, FIG. 5Bis meant to be illustrative only and is not meant to be limiting as tothe layout or particular configuration of elements. The dashboarddisplay shown in FIG. 5B is one way in which a user can be notified.Although FIG. 5B illustrates an example of a buyer's dashboard screen,the features, layout, etc. can also be used to display a supplier'sdashboard screen. As shown in FIG. 5B, a dashboard display has aplurality of sections including a projects section 550, a news feedsection 555, a bookmarks section 565, and a supplier recommendationssection 570.

The projects section 550 can display active and/or archived projects ofthe buyer. The bookmarks section 565 can include bookmarked webpages,user profiles, searches, products, etc. that were bookmarked by thebuyer. The news feed section 555 can include notifications,descriptions, etc. of events relevant to or interesting to the buyer.For example, the news feed section 555 can include indications that oneor more suppliers have been identified to be at risk of being affectedby a supply chain disruption event. In some embodiments, indicators 560can be used to indicate a severity, a confidence level, a score, anurgency level, etc. of the news feed item. The supplier recommendationssection 570 indicates one or more recommended suppliers to the buyer.Each indication of the recommended supplier can include the suppliername and which need the supplier can fill (e.g., which commodity, partnumber, etc.).

As shown in FIG. 3, SCD risk subsystem 110 can include recommendation320. Recommendation 320 can provide to buyers a recommended alternativeto the supplier that is at risk of being affected by an SCD event. Forexample, a buyer can have an outstanding purchase order for o-rings froma first supplier when the first supplier is determined to be(potentially) affected by an SCD event. Recommendation 320 can recommendto the buyer an alternative supplier from whom the buyer can receiveo-rings. The recommended alternative suppliers can be identified usingthe buyer-supplier matching subsystem 115, which is described in greaterdetail below. In an alternative embodiment, the recommended alternativesuppliers can be identified using a business intelligence provider, suchas Covisint Corp.

In some embodiments, SCD risk subsystem 110 can include risk update 315.Although illustrated in the figures as being after notification 310,risk update 315 can be performed at any suitable time, for example afterrisk determination 305. FIG. 6 is a flow diagram of a method forupdating the determination that a supplier is at risk of being affectedby an SCD event in accordance with an illustrative embodiment. Accordingto other exemplary embodiments, additional, fewer, and/or differentelements may be used. Also, the use of arrows in the flow diagram is notmeant to be limiting with respect to the order or flow of operations.Risk update 315 includes receiving a supplier request to update the flag610, receiving a supplier flag dispute 615, verifying that the correctSCD prediction was made 620, determining the supplier's capacity 625,and updating the supplier status 630.

After a supplier is identified as being potentially at risk of beingaffected by an SCD event in operation 305, the supplier can be notifiedof such. That is, the supplier can be notified that it has been flaggedwithin the system as being at risk of being affected by an SCD event.Any suitable method can be used to notify the supplier, such asoperation 530.

In some embodiments, receive a supplier request to update the flag 610can include receiving an indication from a supplier that the supplier'sstatus should be updated. As discussed above with respect to receiverequest for updated prediction 425 (shown in FIG. 4), a supplier canrequest re-evaluation of its status of, for example, being at risk ofbeing affected by an SCD event. Receiving a supplier request to updatethe determination that the supplier is at risk of being affected by anSCD event can be performed using any suitable method. For example, thesupplier can make the request via phone call, SMS text message, email,in-platform-messaging, etc. In some embodiments, receive a supplierrequest to update the flag 610 is not performed. In such embodiments,the system can automatically and/or constantly update the supplier'sstatus based on available information, including information provided bythe supplier.

In some embodiments, the supplier can request an update of thedetermination that the supplier is at risk of being affected by an SCDevent. For example, a supplier can be robbed and its supply of productcan be stolen. Consequently, the system can determine that the supplieris at risk of being affected by the SCD event. After the supplierreplenishes its stock, the supplier can request that the riskdetermination be re-evaluated based on the supplier no longer beingaffected by the SCD event.

In some embodiments, risk update 315 can include receiving a supplierflag dispute 615. As discussed above, a supplier who has been flagged asbeing at risk of being affected by an SCD event may not actually beaffected by the SCD event. That is, in some instances, the wrongprediction can be made. The supplier can notify the system that thesupplier believes that the prediction was incorrect or no longerapplies. The supplier can use any suitable method.

Verifying the correct SCD prediction 620 can re-evaluate thedetermination that the supplier is at risk of being affected by an SCDevent. In some embodiments, verifying the correct SCD prediction 620 canbe automated and/or include algorithms for verifying the riskdetermination. In some embodiments, verifying the correct SCD prediction620 can include a human input and/or evaluation of the riskdetermination. For example, if a supplier disputes a determination thatit is at risk of being affected by an SCD event, verifying the correctSCD prediction 620 can include determining whether a mistake was madeduring the previous determination. Information such as whether thesources that purportedly reported the SCD event actually reported theSCD event (e.g., whether a mistake was made in translating and/orinterpreting a source), how much weight is given to the sources, whetherthe supplier's location is the same location as the SCD event (e.g.,Paris, France, vs. Paris, Tex., U.S.A.), etc. can be used to verify thevalidity of the risk determination.

In some embodiments, if the supplier disputes the risk determination,the supplier can identify information that negates the purported effectof the SCD event. In some embodiments, the system can identify suchinformation. As shown in FIG. 6, risk update 315 can include determininga supplier's capacity 625. For example, a supplier can have a warehousein Omaha, Nebr., explode and the supplier can be determined to be atrisk of being affected by an SCD event (e.g., the explosion). Thesupplier can dispute the determination and supply (or point to)information indicating that the supplier has another warehouse in Fargo,N. Dak., that stores the same product and that the supplier's ability tofulfill orders is unaffected by the explosion in Omaha. Thus,determining a supplier's capacity 630 can include determining that thesupplier has the capability to continue to fulfill orders for itsproduct.

Although not shown in FIG. 6, any suitable reason can be used forreversing the determination that a supplier is at risk of being affectedby an SCD event. Some examples include determining that the supplier hassufficient capacity to fulfill orders; confirming that there is no SCDevent at the supplier's location; determining that a thresholdpercentage of suppliers within a region dispute their status;determining that the supplier's status was disputed from a trustworthysource (e.g., an authenticated email address); confirming with localauthorities that an SCD event has been resolved (e.g., power restored,streets plowed); etc.

In some embodiments, update supplier status 630 can include indicatingthat the supplier is not at risk of being affected by an SCD event. Forexample, a supplier's status can be updated in a database. In someembodiments, based on update supplier status 630, buyers and/orsuppliers can be notified of the change in status using any suitablenotification method, including notification 310. Updating supplierstatus 630 can include un-flagging the supplier within a database.

FIG. 7 is a flow diagram of a buyer-supplier matching subsystem inaccordance with an illustrative embodiment. According to other exemplaryembodiments, additional, fewer, and/or different elements may be used.Also, the use of arrows in the flow diagram is not meant to be limitingwith respect to the order of operations. Buyer-supplier matchingsubsystem 115 includes buyer-supplier matching 705, notification 710,and recommendation improvement 715.

FIG. 8A is a flow diagram of buyer-supplier matching 705 in accordancewith an illustrative embodiment. According to other exemplaryembodiments, additional, fewer, and/or different elements may be used.Also, the use of arrows in the flow diagram is not meant to be limitingwith respect to the order of operations. For example, one or more of theoperations can be performed simultaneously. Buyer-supplier matching 705includes gathering supplier information 810, gathering buyer-supplierassociation information 815, gathering buyer preference information 820,gathering transportation cost information 825, and matching buyers andsuppliers 830.

In some embodiments, buyer-supplier matching 705 can include gatheringsupplier information 810. Information regarding a supplier can begathered and/or received using any suitable method. For example, asupplier information database and/or repository can be used to storesupplier information, such as the supply chain disruption data databaseshown in FIG. 8A. Such a database can include information about one ormore suppliers including suppliers' industries; sectors; capability;capacity; product price; quality; certifications; tooling; equipment;location; rating; on-time delivery record; financial information;ownership information; desired buyer rating; desired buyer financialinformation; desired buyer ownership; previous engagements; feedbackfrom buyers (e.g., numerical rating and/or written); etc. Such adatabase can include information gathered from buyers; suppliers;buyers' websites; suppliers' websites; electronic data exchanges usingeither non-standardized formats or standardized formats (e.g.,electronic data interchange (EDI)); business intelligence providers(e.g., Covisint Corp.); industry associations; consultants; newsorganizations; governments; etc.

In some embodiments, buyer feedback can include whether a supplier hasbeen endorsed, qualified, and/or approved by one or more buyers. Abuyer's endorsement can be an indication that the buyer has beensatisfied with the supplier's product and/or service or otherwisecommend the supplier or recommend the use of the supplier. For example,a buyer's endorsement can include a discrete endorsement (e.g., “thumbsup,” “thumbs down,” or neutral; a numerical rating or score; a binaryindication such as recommended or neutral; etc.). According to otherexemplary embodiments, a buyer's endorsement can include a testimonial,a description, a written review, etc. A buyer can qualify the use of asupplier. The buyer's qualification of a supplier can be an indicationby the buyer that the supplier is qualified to provide the product orservice of the supplier. For example, a buyer can qualify a supplier,thereby advancing the relationship between the buyer and the supplier.The qualification of the supplier can allow the supplier to providequotes to the buyer. The buyer can also approve a supplier. Approval ofa supplier can be an indication by the buyer that the supplier isapproved to do business with the buyer. A buyer can review variousaspects of a supplier before approving a supplier. For example, a buyercan review agreements with other suppliers such as exclusive purchaseagreements, manufacturing capabilities of the supplier, government orindustry certifications of the supplier, product quality of thesupplier, etc.

Some examples of industries include automotive; medical device; consumerproducts; infrastructure; energy; mining; chemical; pharmaceutical; rawmaterials; aerospace; food and/or beverages; heavy-duty truckmanufacturing; etc. Some examples of sectors include manufacturer;distributor; wholesaler; retailer; etc. Some examples of certificationscan include TS 16949; ISO 9001; ISO 14001; ISO 13485; governmentalcertifications; ability to import/export with certain countries;industry certifications; etc. Some examples of a supplier's capabilityinclude machining; machining carbon fiber (e.g., prototypes);prototyping; casting; casting carbon fiber; plastic manufacturing;plastic thermoforming; plastic injection molding; molding; stamping;welding; painting; powder coating; ability to work with materials suchas polyurethane, urethane, adhesives, etc.; ablation casting; bending;air freight; etc.

In some embodiments, the supplier information database can includecontact information. The contact information can include contactinformation for sales representatives, managers, company presidents orleaders (e.g., C-level executives), etc. The contact information can beupdated by the supplier as the contact information changes. For example,a sales representative may leave employment by a supplier and the salesrepresentative may not provide his or her customers with a method ofcontacting the supplier once the sales representative leaves. Thus, insome embodiments, system 100 can allow users to find up-to-date contactinformation for suppliers or notify users when contact informationchanges.

In some embodiments, the supplier information database can includecapability terms and/or capability term chains. Each capability term candescribe an aspect of the supplier. Capability term chains can containmultiple capability terms. The capability term chains can be used toprovide a brief description that is more specific than the capabilityterms themselves. For example, a supplier of wiring harnesses formotorcycles can be associated with capability terms including“automotive,” “motorcycle,” “manufacturer,” and “wire harness.” The samesupplier can be associated with capability term chains such as“motorcycle; wire harness,” “automotive; wire harness,” “manufacturer;wire harness,” etc. In some embodiments, the order of the capabilityterms in capability term chains can be ignored. Thus, “motorcycle; wireharness” can be equivalent to “wire harness; motorcycle.” In someembodiments, the capability terms can be chosen amongst a predeterminedlist. According to other exemplary embodiments, the capability terms canbe any suitable term. In some embodiments, the supplier can choose thecapability terms and/or term chains associated with the supplier.According to other exemplary embodiments, a system administrator,buyers, etc. can choose the capability terms and/or term chainsassociated with the supplier. Thus, in some embodiments, a buyersearching for a supplier of motorcycle wiring harnesses can search forsuppliers associated with the term chain “motorcycle; wire harness.”

In some embodiments, the capability terms and/or capability term chainscan be used to search for buyers and/or suppliers. In some embodiments,the capability terms and/or capability term chains can be displayed on aprofile page of the buyer/supplier, next to the name of thebuyer/supplier when displayed (e.g., in news feed section 555 and/orsupplier recommendations section 570 of FIG. 5B), etc.

FIG. 5C is an illustration of a user profile display in accordance withan illustrative embodiment. According to other exemplary embodiments,additional, fewer, and/or different elements may be used. Also, FIG. 5Cis meant to be illustrative only and is not meant to be limiting as tothe layout or particular configuration of elements. A user profiledisplay can display information of a user of the SCM system 105. Theusers can be, for example, employees of buyers or suppliers. As shown inFIG. 5C, a user profile display can include identification informationsection 575. The identification information section 575 can includeinformation such as a user's name (e.g., William Crane), title (e.g.,Founder & CEO), and contact information (e.g.,william.crane@industrystar.com). The user profile display can alsoinclude a user needs section 580 that can identify the needs of the userand/or the user's employers (e.g., IndustryStar and IndustryStarSolutions LLC). The user needs section 580 can include one or morecapability terms and/or capability term chains 590 (e.g., “motorcycle;manufacturer,” “consumer products; manufacturer,” “automotive;manufacturer; stamping,” “manufacturer; wire harness,” “plastic;injection molding,” and “wire harness”) indicating areas in which theuser is seeking products. The user needs section 580 can indicate whichneeds are current needs (e.g., one-time needs) and which needs areongoing needs. The user profile display can also include an employeridentification section 585 that can identify which companies the usercurrently works for and/or which companies the user previously workedfor. The employer identification section 580 can include the name of thecompany, the title the user has (or had) at the company, one or moreaddresses of the company, contact information of the company (e.g.,phone number, email address, website), etc.

FIG. 5D is an illustration of a company profile display in accordancewith an illustrative embodiment. According to other exemplaryembodiments, additional, fewer, and/or different elements may be used.Also, FIG. 5D is meant to be illustrative only and is not meant to belimiting as to the layout or particular configuration of elements. Acompany profile page can include identification section 591 that caninclude identification information such as a company name (e.g., 3Dimensional Services), contact information such as a website, address,phone number, email address, etc., and a map indicating one or morelocations of the company. The company profile page can also includesupplier information section 592 that can include sub-sections withidentifying information such as industries, sectors, certifications,ownership, and financial information. Supplier information section 592can use one or more capability terms and/or capability term chains 590(e.g., “automotive,” “motorcycle” and “agriculture” to identify theindustries of the company and “manufacturer” to identify sectors of thecompany). Financial information can include one or more financialaspects of the company such as the Z-Score, the quick ratio, or thecurrent ratio of the company. The company profile page also includes acapabilities section that lists capabilities of the company. Thecapabilities section can use one or more capability terms and/orcapability term chains 590 (e.g., “metal,” “plastic,” “rubber,”“assembly,” “fabricating,” “machining,” “seals and gaskets,” “stamping,”“laser cutting,” “injection molding,” and “exterior”).

In some embodiments, one or more items of the company profile displaycan be selected by a viewer of the company profile display. Selecting anitem can display greater detail of the item. For example, by selectingthe company financial information item of the company profile display,greater detail of the company's financial information can be displayed.FIG. 5E is an illustration of a display of a company's financialinformation in accordance with an illustrative embodiment. According toother exemplary embodiments, additional, fewer, and/or differentelements may be used. Also, FIG. 5D is meant to be illustrative only andis not meant to be limiting as to the layout or particular configurationof elements. As shown in FIG. 5D, a column of financial informationaspects 594 can be shown and corresponding data for the aspects for aparticular year (e.g., 2014) can be shown in column 595. Although FIG.5D shows one year's information, any suitable number of years'information can be displayed in additional columns. The variousfinancial information aspects can include a Z-Score, a current ratio, aquick ratio, an inventory turnover ratio, a day's sales of inventoryratio, a balance sheet, current assets, long-term assets, currentliabilities, income statement, a cash flow statement, and/or otherinformation such as a market value of equity. The balance sheetinformation can be broken down into aspects such as cash, accountsreceivable, prepaid expenses, and inventory. The current assets can bebroken down into aspects such as plants or manufacturing facilities,property, and equipment. The long-term assets can be broken down intoaspects such as accounts payable, notes or other financial instrumentspayable, and accrued expenses payable. The income statement can bebroken down into aspects such as sales, cost of goods sold, and earningsbefore interest and tax (EBIT).

In some embodiments, buyer-supplier matching 705 can include gatheringbuyer-supplier association information 815. Buyer-supplier associationinformation can be information related to relationships between buyersand suppliers. Buyer-supplier association information can be gatheredand/or received using any suitable method. For example, a database,list, repository, etc. can be maintained that keeps track ofbuyer-supplier associations, such as the buyer-supplier associationdatabase shown in FIG. 8A. Such a database can include informationgathered from buyers who supply a list of current suppliers; informationgathered from suppliers who provide a list of current buyers; pendingbuyer-supplier transactions; a history of a buyer who rated a supplier;a history of a supplier who rated a buyer; a buyer-supplier interactionhistory (e.g., via messages, emails, complaints); a buyer-suppliertransaction history; etc. Such a database can include informationgathered from buyers; suppliers; buyers' websites; suppliers' websites;electronic data exchanges using either non-standardized formats orstandardized formats (e.g., electronic data interchange (EDI)); businessintelligence providers (e.g., Covisint Corp.); industry associations;consultants; news organizations; governments; etc.

In some embodiments, buyer-supplier matching 705 can include gatheringbuyer preference information 820. Buyer preference information caninclude characteristics and/or features of a supplier and/or productthat a buyer requires and/or prefers. For example, a buyer may not wishto use a supplier that already supplies the buyer's competitor. Inanother example, a buyer can require specific tolerances and/ormanufacturing details. The buyer preference information can includebuyers' need; volume; desired cost; desired quality; desiredcertifications; desired materials of construction; delivery location;desired rating of the supplier; desired delivery time; desired on-timedelivery rating of the supplier; desired financial information of thesupplier (e.g., minimum size of the supplier); desired ownership of thesupplier; desired existing customers of the supplier; desired socialconsiderations of the supplier (e.g., energy efficiency, pollution,labor, etc.); etc. In some embodiments, buyer-supplier matching 705 caninclude gathering supplier preference information similar to the buyerpreference information.

In some embodiments, buyer preference information can include buyerinformation. Such buyer information can be stored in a database and/orrepository, such as the buyer information database shown in FIG. 8A. Thebuyer information can include buyers' industries; sectors;certifications; location; rating; financial information; ownership;preference for specific suppliers (or types of suppliers); previouspreference for product cost; previous preference for product quality;previous preference for supplier certifications; previous preference forsupplier rating; previous preference for on-time delivery rating of asupplier; previous preference for desired supplier financialinformation; previous preference for desired supplier ownership;previous engagements with the supplier or another supplier; feedbackabout the buyer from a supplier (e.g., numerical rating and/or written);etc. In some embodiments, the buyer preference information database caninclude capability terms and/or capability term chains that the buyer islooking for in a supplier.

In some embodiments, buyer-supplier matching 705 can include gatheringtransportation cost information 825. Any suitable method of gatheringtransportation cost information can be used. Transportation costs canaffect the net cost of a supplier's parts. For example, it mayultimately be cheaper for a buyer to obtain a part from a nearbysupplier than from a distant supplier even though the per-unit cost ofthe nearby supplier is higher. That is, the cost to ship the productsfrom the distant supplier to the buyer can be greater than the costdifference. In some embodiments, the transportation cost information canbe stored in a database, a list, a repository, etc., such as thetransportation cost database shown in FIG. 8A. The transportation costinformation can include information from historical cost estimatesleveraged from past quotes of suppliers; transportation providers; thirdparty logistics providers (3PLs); transportation exchange websites suchas FreightQuote.com; industry association reports; government data(e.g., gasoline prices, diesel prices, tariffs, etc.); etc.

In some embodiments, buyer-supplier matching 705 can include matchingbuyers and suppliers 830. Matching buyers and suppliers 830 can use someor all of the information gathered in operations 810-825. Matchingbuyers and suppliers 830 can include identifying the suppliers that bestmeet the buyer's needs and/or preferences. Similarly, matching buyersand suppliers 830 can include identifying the buyers that best meet thesupplier's capabilities and/or preferences.

In some embodiments, matching buyers and suppliers 830 can includedetermining a matching score. The matching score can include aconsideration as to whether a supplier has been endorsed, qualified,and/or approved by the buyer and whether the buyer has been endorsed,qualified, and/or approved by the seller. The matching score can bebased on a comparison of the buyer's need and the supplier's capability;the buyer's volume of need and the supplier's capacity; the buyer'sdesired cost and the supplier's price; the buyer's desired quality andthe supplier's quality; the buyer's desired certifications and thesupplier's certifications; the buyer's location of need and thesupplier's location and/or shipping capabilities; the buyer's desiredsupplier rating and the supplier's rating; the buyer's on-time deliverypreference and the supplier's on-time delivery record; the buyer'sdesired supplier financial information and the supplier's financialinformation; the buyer's desired supplier ownership and the supplier'sownership; the buyer's industries and the supplier's industries; thebuyer's sectors and the supplier's sectors; the buyer's previouspreference of desired cost and the supplier's price; the buyer'sprevious preference of desired quality and the supplier's quality; thebuyer's previous preference of desired certifications and the supplier'scertifications; the buyer's previous preference of desired supplierrating and the supplier's rating; the buyer's previous on-time deliverypreference and the supplier's on-time delivery record; the buyer'sprevious preference of desired supplier financial information and thesupplier's financial information; the buyer's previous desired supplierownership and the supplier's ownership; the supplier's desired buyerrating and the buyer's rating; the supplier's desired buyer financialinformation and the buyer's financial information; the supplier'sdesired buyer ownership and the buyer's ownership; capability termsand/or capability term chains of the supplier and capability termsand/or capability term chains of the buyer; etc. In some embodiments,the matching score can be based on other factors such as the buyer'spreference for specific suppliers or types of suppliers.

In some embodiments, one or more of the factors (e.g., the comparisons)can be weighted, using any suitable method. In some embodiments,different weights can be applied to the various factors. In oneembodiment, the weights of the various factors can be adjusted toincrease accuracy of buyer-supplier matches. Adjustments to the weightsmay be made based on feedback from buyers and/or suppliers (e.g., whichcriteria are most important); metrics related to the success of matchingbuyers and suppliers; the nature of the particular industry; the time ofyear; the desired timing of delivery; etc. Such examples are merelyillustrative. Other factors now known or later developed may be used toadjust the weight assigned to various factors.

In some embodiments, the weights applied to a buyer can be changed basedon the weights of other buyers. That is, the weights of a buyer can beadjusted based on what similar buyers prefer. The other buyers can, forexample, be in the same industry, in the same geographic region, etc. asthe buyer. For example, SCM system 105 can determine that buyers in thebotany industry are generally increasing the weight of products' pricewhen matched to a supplier. In such an example, the product price weightfor a buyer in the botany industry can be automatically increased tomatch the increase in weight of the industry in general. In anotherexample, if buyers in Detroit, Michigan, generally increase the weightof on-time delivery during winter months, the on-time delivery weight ofa buyer in Detroit can be automatically increased by SCM system 105during winter months.

For example, the comparison between a buyer's volume of need and asupplier's capacity can be assigned a relatively large weight. If asupplier's capacity is unable to fulfill a buyer's volume of need, theaggregate matching score can reflect that the match quality between thebuyer and the supplier is low. Thus, the supplier can be ranked low forthe buyer. In one embodiment, if a supplier's capacity is much largerthan a buyer's volume of need, the aggregate matching score can reflectthat the match quality between the buyer and the supplier is low. Thus,the supplier can be ranked low for the buyer. In such an example, thesupplier can be ranked low for the buyer because the supplier may not besufficiently motivated or willing to supply product to a buyer with arelatively low need. However, in some embodiments, a supplier canindicate to the system that the difference between the supplier'scapability and the buyer's need is not an important factor to thesupplier and the comparison can be weighted less when the supplier'scapability exceeds the buyer's need. Similarly, in another example, abuyer may indicate that it is acceptable to purchase the same productfrom several suppliers. Thus, in such an example, the comparison betweenthe supplier's capability and the buyer's needs can be weighted less.

In some embodiments, the matching score can be a difference score. Insuch an embodiment, the difference between a buyer's volume of need anda supplier's capacity can be high (e.g., a supplier cannot fulfill abuyer's volume of need or a buyer's need is much smaller than asupplier's capacity) thereby indicating that the match quality of thebuyer and the supplier is low.

In some embodiments, a matching score can indicate a higher qualitymatch based on previous engagements of a buyer with a supplier. Forexample, if a buyer previously purchased a product from the supplier,and the buyer is searching for a supplier for the product (or adifferent product), the matching score of the supplier for the buyer canbe increased based on the previous purchase. Thus, in some embodiments,a preference can be made for suppliers (and/or buyers) who have anexisting (or previous) relationship with the buyer (and/or supplier).

In some embodiments, buyer-supplier matching subsystem 115 can includenotification 710. FIG. 8B is a flow diagram of a method for notifyingusers of a buyer-supplier match in accordance with an illustrativeembodiment. According to other exemplary embodiments, additional, fewer,and/or different elements can be used. Also, the use of arrows or a flowdiagram is not meant to be limiting with respect to the order or flow ofoperations. Notification 710 includes notifying buyers 835 and notifyingsuppliers 845.

In some embodiments, notifying buyers 835 can include notifying a buyerof a supplier with whom the buyer may be interested in establishing (orfurthering) a relationship with. Similarly, in some embodiments,notifying suppliers 845 can include notifying a supplier of a buyer withwhom the supplier may be interested in establishing (or furthering) arelationship with. Notification 710 can notify buyers and/or suppliersof matches using any suitable method. For example, notification 710 caninclude displaying matches next to a search result and/or as a searchresult; displaying the matches on the buyer's dashboard, home page,etc.; displaying a message on the supplier's information page when thebuyer views the supplier's information page; displaying a message on thebuyer's information page when the supplier views the buyer's informationpage; emailing the buyer and/or supplier; calling the buyer and/orsupplier; sending a fax to the buyer and/or supplier; sending an SMStext message to the buyer and/or supplier; displaying the matches on agraphical information system (GIS) display; etc.

For each buyer, suppliers can be ranked based on the aggregate matchingscores of the suppliers. Similarly, for each supplier, buyers can beranked based on the aggregate matching scores of the buyers. In someembodiments, all matches can be presented to the buyer and/or supplier.In other embodiments, only some of the matches can be presented to thebuyer and/or supplier. For example, the top ten matches can bepresented. In another example, all matches with a matching score above athreshold can be presented.

In some embodiments, notify buyers 835 and/or notify suppliers 845 caninclude a graphical representation of the recommendations. FIG. 8D is anillustration of a graphical representation of recommendations inaccordance with an illustrative embodiment. According to other exemplaryembodiments, additional, fewer, and/or different elements may be used.Also, FIG. 8D is meant to be illustrative only and is not meant to belimiting as to the layout or particular configuration of elements.Although FIG. 8D is an illustration of an example of displaying to abuyer a list of recommended suppliers, the features, layout, etc. canalso be used to display to a supplier a list of recommended buyers. Asshown in FIG. 8D, a graphical display of recommended suppliers includesa plurality of columns 891. Each column 891 can be used to displayinformation regarding a particular recommended supplier. Although FIG.8D illustrates displaying four recommended suppliers, any suitablenumber of recommended suppliers can be displayed. Additionally, althoughinformation regarding each supplier is contained in a column 891, rowscan be used According to other exemplary embodiments (e.g., by swappingcolumns 891 with rows 892). Information in each column 891 can includethe name of a supplier, which stage of communication the buyer andsupplier are at (e.g., a communication such as an invitation was sent, acommunication was received, a request for quote (RFQ) was sent, an RFQwas received, an RFQ was rejected, an RFQ was accepted, etc.), statusinformation (e.g., whether a non-disclosure agreement has been executed,whether a memorandum of understanding has been executed, etc.), anindication of whether the supplier is capable of satisfying the buyer'sneeds, whether the supplier is at risk of being affected by a supplychain disruption event, etc. Such information can be displayed via text,icons, check marks, “X” symbols, color coding, etc.

As shown in FIG. 8D, the graphical display of recommended suppliersincludes a row 892. According to other exemplary embodiments, aplurality of rows 892 can be displayed. Each row 892 can displayinformation related to a need of the buyer, an aspect of a need of thebuyer, a commodity, a part number, etc. The information displayed ineach row 892 can include a name or description of the need of the buyer(or a part number, etc.) and an indication of whether each supplier cansatisfy the need of the buyer.

The graphical display of recommended suppliers includes rows 893. Rows893 can display the interaction history of the buyer and a selectedsupplier. The selected supplier can be chosen amongst the recommendedsuppliers. Each row 893 can include information of an interactionactivity between the supplier and the buyer. The information can includethe type of interaction (e.g., a communication such as an invitation wassent, a communication was received, an RFQ was sent, etc.), a timestampof the interaction activity (e.g., of when the entry was last modified),an identification of one or more acting individuals (e.g., who sent themessage, who accepted the RFQ, etc.), comments or notes, a descriptionof the interaction activity, etc.

In some embodiments, suppliers can provide a bid for a buyer's needs.For example, potential buyers for a supplier can be identified and thesupplier can be notified of such potential buyers. In some embodiments,the needs of a buyer are made available to all users of SCM system 105.The supplier can review the needs of the buyer, and provide a bid to thebuyer to satisfy the buyer's need. In such an example, the potentialbuyers need not send a request for a quotation or bid to the supplier.Rather, the supplier can find potential buyers (e.g., via buyer-suppliermatching subsystem 115) and provide bids to the potential buyers inresponse to the potential buyers being identified as potential buyers orrecommended buyers.

In some embodiments, buyer-supplier matching subsystem 115 can includerecommendation improvement 715. FIG. 8C is a flow diagram of a methodfor improving recommendations in accordance with an illustrativeembodiment. According to other exemplary embodiments, additional, fewer,and/or different elements may be used. Also, the use of arrows and aflow diagram is not meant to be limiting with respect to the order orflow of operations. Recommendation improvement 715 includes receiving abuyer's positive endorsement of a supplier 850, increasing thesupplier's future ranking 855, receiving a buyer's positive endorsementof a supplier type 860, adjusting weights for matching 865, receiving abuyer's negative endorsement of a supplier 870, adjusting weights formatching 875, decreasing the supplier's future ranking 880, receiving asupplier inquiry, and suggesting areas for improvement 890.

Recommendation improvement 715 can adjust weights of comparisons and/orfactors used in determining matches in buyer-supplier matching 705 toimprove the matches presented to buyers and/or suppliers. In someembodiments, feedback from a buyer and/or a supplier can be received.The feedback can be related to a supplier (or a buyer) that wasrecommended to and/or matched with the buyer (or the supplier). Based onthe feedback, the weights of the considerations can be adjusted suchthat future matches and/or recommendations are improved. Accordingly, insome embodiments, the more buyer-supplier matching subsystem 115 isused, the matches or recommendations can be improved because moreinformation is available to identify the most appropriate buyer orsupplier.

For example, if a buyer provides a positive endorsement (e.g., providesa positive review or positive feedback) a supplier that was recommendedto the buyer (operation 850), then the supplier's ranking can beincreased in future matches (operation 855). In some embodiments, thesupplier's ranking can be increased with regard to the buyer that likedthe supplier. According to other exemplary embodiments, the supplier'sranking can be increased with regard to all potential buyers. In anotherexample, a buyer can provide a positive endorsement (e.g., provide apositive review or positive feedback) multiple suppliers and/or a typeof supplier (operation 860). In some embodiments, recommendationimprovement 715 can identify one or more features that the multiplesuppliers share and the weight of such features can be increased infuture matching score calculations (operation 865). In anotherembodiment, the buyer can identify one or more features that the buyerlikes (operation 860) and the weight of such features can be increasedin future matching score calculations (operation 865). In someembodiments, a positive endorsement can include a buyer qualifyingand/or approving a seller. If a supplier has been qualified or approvedby a buyer, the supplier can be ranked higher than a supplier that hasnot been qualified or approved by the buyer. In some embodiments, asupplier that has been approved can be ranked higher than a supplierthat has been qualified.

Similarly, if a buyer provides a negative endorsement (e.g., provides anegative review or negative feedback) a supplier that was recommended tothe buyer (operation 870), then the supplier's ranking can be decreasedin future matches (operation 880). In some embodiments, the supplier'sranking can be decreased with regard to the buyer that liked thesupplier. According to other exemplary embodiments, the supplier'sranking can be decreased with regard to all potential buyers.

In another example, a buyer can provide a negative endorsement (e.g.,provide a negative review or negative feedback) multiple suppliersand/or a type of supplier. In some embodiments, recommendationimprovement 715 can identify one or more features that the multiplesuppliers share and the weight of such features can be decreased infuture matching score calculations. In another embodiment, the buyer canidentify one or more features that the buyer dislikes and the weight ofsuch features can be decreased in future matching score calculations(operation 875). Although the above examples include buyers liking ordisliking suppliers, the same examples can apply to suppliers liking ordisliking buyers in rankings of buyers for suppliers. Further, althoughthe above examples include buyers liking or disliking suppliers thathave been previously recommended, the same examples can apply tosuppliers (or buyers) that have not been previously recommended to thebuyer.

In some embodiments, receive supplier inquiry 885 can include a supplierinquiring into the number of recommendations of the supplier that aremade to buyers. For example, a supplier's amount of new customers candecrease while the supplier's competitors' amount of new customers canincrease. The supplier can inquire as to why the supplier is not beingrecommended as often as its competitors. In such embodiments, thecomponents that make up the matching score of the supplier (e.g., thecomparisons between the supplier and the buyer, the weights, reviews,etc.) can be compared to the matching scores of the supplier'scompetitors. After the comparison of matching scores, the system cannotify the supplier of areas in which the supplier's competitors scorebetter than the supplier (operation 890). Such areas can be areas inwhich the supplier can improve to gain more recommendations in thefuture. In some embodiments, the system can automatically identify forsuppliers (and/or buyers) areas in which to improve to increase itsranking. In some embodiments, the supplier's (and/or the buyer's)matching score and/or matching score components can be displayed to thesupplier via, e.g., a dashboard view, a home screen, etc.

In some embodiments, SCM system 105 can include a supply chainmanagement system that incorporates a crowd-sourced capability ratingsubsystem that can leverage data from a plurality of system users tocrowd-source buyer and supplier capability ratings. Such a supply chainmanagement system provides advantages over traditional formats in whichindividual companies maintained information on, and rated, othercompanies using their own interactions. Using a crowd-sourcedcapability-rating subsystem, even if a buyer is seeking to engage asupplier in an industry in which the buyer had never previously engaged,the buyer can have access to relevant information about the capabilitiesof the supplier without engaging in a trial-and-error approach tofinding the most suitable suppliers.

FIG. 9 is a flow diagram of a rating subsystem in accordance with anillustrative embodiment. According to other exemplary embodiments,additional, fewer, and/or different elements may be used. Further, theuse of arrows is not meant to be limiting with respect to the order orflow of operations. The rating subsystem 120 can include determininguser scores 910, displaying user scores 915, and updating user scores920. In some embodiments, operations 910-920 are performedsimultaneously and/or constantly.

In some embodiments, the rating subsystem 120 can be a crowd-sourcedrating system. That is, users (e.g., buyers and suppliers) can be ratedbased on input from a plurality of sources. In some embodiments, theplurality of sources can include other users. The user ratings can bebased on numerical scores and/or written reviews. In some embodiments,user ratings can be based using only trusted sources, such as buyers andsuppliers with a confirmed identity. In some embodiments, only otherusers that have a relationship with a rated user can contribute to theuser's rating. In yet other embodiments, any suitable source ofinformation can be used to rate users.

FIG. 10A is a flow diagram of a method for calculating user scores inaccordance with an illustrative embodiment. According to other exemplaryembodiments, additional, fewer, and/or different elements may be used.Further, the use of arrows is not meant to be limiting with respect tothe order or flow of operations. Determining user scores 910 can includegathering supplier information 1010, gathering buyer information 1015,and calculating user scores 1020.

Gathering supplier information 1010 can include gathering, retrieving,and/or receiving information regarding a supplier. Any suitable methodcan be used to gather supplier information. For example, a supplierinformation database and/or repository can be used to store supplierinformation, such as the supplier information database shown in FIG.10A. In some embodiments, the supplier information database of FIG. 10Ais the same as the supplier information database of FIG. 8A. Such adatabase can include information about one or more suppliers includingsuppliers' industries; sectors; capability; capacity; product price;quality; certifications; tooling; equipment; location; on-time deliveryrecord; financial information; ownership information; desired buyerrating; desired buyer financial information; desired buyer ownership;previous engagements; feedback from buyers (e.g., numerical ratingand/or written); etc. Such a database can include information gatheredfrom buyers; suppliers; buyers' websites; suppliers' websites;electronic data exchanges using either non-standardized formats orstandardized formats (e.g., electronic data interchange (EDI)); businessintelligence providers (e.g., Covisint Corp.); industry associations;consultants; news organizations; governments; etc. In some embodiments,information regarding the suppliers of a supplier can be included in thesupplier information database. For example, second, third, etc. tiersupplier information can be used to determine a first tier supplier'sscore. Thus, in some embodiments, if a supplier uses risky suppliersitself, the supplier can receive a lower score.

Gathering buyer information 1015 can include gathering, retrieving,and/or receiving information regarding a buyer. Any suitable method canbe used to gather buyer information. For example, a buyer informationdatabase and/or repository can be used to store buyer information, suchas the buyer information database shown in FIG. 10A. In someembodiments, the buyer information database of FIG. 10A is the same asthe buyer information database of FIG. 8A. Such a database can includeinformation about one or more buyers including buyers' need; volume;desired cost; desired quality; desired certifications; desired materialsof construction; delivery location; delivery time requirement; desiredon-time delivery rating of the supplier; desired financial informationof the supplier (e.g., minimum size of the supplier); desired ownershipof the supplier; existing customers of the supplier; desired socialconsiderations of the supplier (e.g., energy efficiency, pollution,labor, etc.); purchase order history; suppliers the buyers have workedwith; feedback from suppliers; etc. Such information can includehistorical information (e.g., buyers' past need) and current information(e.g., buyers' current need).

In some embodiments, either gathering supplier information 1010 orgathering buyer information 1015 can be performed. Similarly, in someembodiments, gathering supplier information 1010 and/or gathering buyerinformation 1015 can include gathering information on a single user. Insome embodiments, gathering supplier information 1010 and gatheringbuyer information 1015 can occur simultaneously, constantly, and/orperiodically.

Calculating user scores 1020 can including determining a rating of auser. One or more user scores can be calculated using the informationgathered about the user. The range of numbers for a particular score(e.g., equipment or tooling) can be any suitable range. In someembodiments, all scores have the same possible range, but can havedifferent weights. In other embodiments, scores can have differentranges. In some embodiments, each user can have one or more ratings.Some types of ratings can include a capability score, a capacity score,a quality score, an on-time delivery score, a price score, a financialscore, an overall (e.g., aggregate) score, etc. In some embodiments,calculating user scores 1020 can include calculating scores of multipleusers. In some embodiments, a user score can include a numerical score,a percentile score, and/or a written score (e.g., a written review, adescription, etc.). In some instances, the written reviews,descriptions, etc. can increase a user rating score by a determinedamount (e.g., ten points, one point, 0.1 points, 0.01 points, etc.) fora positive review and can decrease the user rating score by the samedetermined amount or a different determined amount for negative reviews.In such embodiments, neutral reviews may not affect the user ratingscore. In some instances, automatic systems can be used to analyze thetext of written reviews or descriptions to determine whether the writtenreview or description is positive, negative, or neutral. In otherembodiments, the user submitting the written review or description canprovide whether the review is positive, negative, or neutral.

A user score can be calculated using information from multiple sources.Thus, in some embodiments, the user score can be determined usingcrowd-sourcing. The weight of the information from the sources can bedifferent depending upon the type of information and/or the source. Forexample, when calculating an on-time delivery score of a supplier,information gathered from the supplier's website regarding its ownon-time delivery record can be weighted less than information gatheredfrom buyers who have given feedback regarding whether deliveries fromthe supplier were on time. In another example, feedback regarding asupplier from buyers with a verified identity can be weighted higherthan feedback regarding the supplier from buyers whose identity has notbeen verified. Similarly, in some embodiments, feedback regarding asupplier from a buyer whose purchase from the supplier can be verifiedcan be weighted higher than feedback regarding the supplier from a buyerwhose purchase from the supplier is not verified.

In some embodiments, information considered when calculating a score canbe weighted based on time. For example, older information can beweighted less than newer information. In some embodiments, an overalluser score can be calculated by combining various other scores of theuser. In such embodiments, the various other scores of the user can beweighted differently. In some embodiments, the weights of the variousother scores used to calculate an overall user score can be the same forall users. For example, a price score can be 30% of an overall score forall users (or all buyers, all suppliers, or any subset thereof).According to other exemplary embodiments, the weights of the variousscores used to calculate an overall score are the same for all userswithin a group. For example, the weights for calculating overall scorescan be the same for all automotive buyers whose revenue is greater than$4 million per year. In such an example, the weights used to calculatethe overall scores of automotive buyers whose revenue is greater than $4million per year can be different than the weights used to calculate theoverall scores of chemical manufacturers whose revenue is greater than$50 billion per year.

In some embodiments, the rating subsystem 120 can include displayinguser scores 915. In some embodiments, one or more of each user's scorescan be displayed. In some embodiments, only one score (e.g., a user'soverall score) is displayed. A user's score can be displayed in anysuitable manner. For example, a user's score can be displayed next tothe user's name in a list (e.g., search results, rankings, etc.); on theuser's information (e.g., profile) page; on the user's dashboard and/orhome screen; on a geographical information system (GIS) display; etc.

In some embodiments, the rating subsystem 120 can include updating auser's score 920. FIG. 10B is a flow diagram of a method of updating auser's score in accordance with an illustrative embodiment. According toother exemplary embodiments, additional, fewer, and/or differentelements may be used. Also, the use of arrows and a flow diagram is notmeant to be limiting with respect to the order or flow of operations.Updating a user's score 920 includes receiving a request 1030, adjustingconsidered information sources 1035, and recalculating user scores 1040.

In some embodiments, updating a user's score can include re-determiningthe user's score via operation 910. In some embodiments, updating auser's score can include dispute resolution. For example, receiving arequest 1030 can include receiving an indication that a user disputesits score. In such an example, the disputed of the score can include ageneral dispute (e.g., a score is too low) or can include a specificdispute (e.g., a source used to determine the user's score should nothave been used). Based on the indication that the user disputes itsscore, one or more changes can be made, and the user's score can bere-determined. For example, adjusting considered information sources1035 can include adding and/or removing sources of information from thepool of information used to determine the user's score. In someembodiments, the changes can include adjustments to weights used tocalculate the user's score. The changes can be made automatically or canbe made by a system administrator. In some embodiments, any and/or allchanges can be approved by a system administrator.

For example, a supplier can dispute its on-time delivery score. Thesupplier can identify a source of information, such as a bad review,that the supplier suggests should not be considered in determining theon-time delivery score. For example, the bad review can be made from auser that has never purchased a product from the supplier and, thus, hasno basis for its bad review of the supplier. The bad review can then beeliminated from the information used to determine the on-time deliveryscore and the on-time delivery score can be re-calculated in recalculateuser score 1040.

FIG. 11 is a block diagram of a controller in accordance with anillustrative embodiment. According to other exemplary embodiments,additional, fewer, and/or different elements may be used. A controller1100 can include a processor 1105, a memory 1110, a communicationstransceiver 1120, a power source 1130, and a user interface 1125. TheSCM system 105 can include one or more controllers 1100.

In some embodiments, controller 1100 can include processor 1105.Processor 1105 can be configured to carry out and/or cause to be carriedout one or more operations described herein. Processor 1105 can executeinstructions as known to those skilled in the art. The instructions maybe carried out by one or more special purpose computers, logic circuits(e.g., programmable logic circuits (PLC)), and/or hardware circuits.Thus, processor 1105 may be implemented in hardware, firmware, software,or any combination of these methods. The term “execution” is the processof running an application or the carrying out of the operation calledfor by an instruction. The instructions may be written using one or moreprogramming language, scripting language, assembly language, etc.Processor 1105 executes an instruction, meaning that it performs theoperations called for by that instruction. Processor 1105 operablycouples with memory 1110, communications transceiver 1120, power source1130, user interface 1125, etc. to receive, to send, and to processinformation and to control the operations of the controller 1100.Processor 1105 may retrieve a set of instructions from a permanentmemory device such as a read-only memory (ROM) device and copy theinstructions in an executable form to a temporary memory device that isgenerally some form of random access memory (RAM). Controller 1200 mayinclude a plurality of processors that use the same or a differentprocessing technology. In an illustrative embodiment, the instructionsmay be stored in memory 1110.

In some embodiments, controller 1100 can include memory 1110. Memory1110 can be an electronic holding place or storage for information sothat the information can be accessed by processor 1205 using anysuitable method. Memory 1110 can include, but is not limited to, anytype of random access memory (RAM), any type of read-only memory (ROM),any type of flash memory, etc. such as magnetic storage devices (e.g.,hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g.,compact disk (CD), digital versatile disk (DVD), etc.), smart cards,flash memory devices, etc. Controller 1100 may have one or morecomputer-readable media that use the same or a different memory mediatechnology. Controller 1100 may have one or more drives that support theloading of a memory medium such as a CD, a DVD, a flash memory card,etc.

In some embodiments, controller 1100 can include a communicationstransceiver 1120. Communications transceiver 1120 can be configured toreceive and/or transmit information. In some embodiments, communicationstransceiver 1120 can communicate information via a wired connection,such as an Ethernet connection, one or more twisted pair wires, coaxialcables, fiber optic cables, etc. In some embodiments, communicationstransceiver 1120 can communicate information via a wireless connectionusing microwaves, infrared waves, radio waves, spread spectrumtechnologies, satellites, etc. Communications transceiver 1120 can beconfigured to communicate with another device using cellular networks,local area networks, wide area networks, the Internet, etc. In someembodiments, one or more of the elements of controller 1100 communicatevia wired or wireless communications.

In some embodiments, controller 1100 can include power source 1130.Power source 1130 can be configured to provide electrical power to oneor more elements of controller 1100. In some embodiments, power source1130 can include an alternating power source, such as available linevoltage (e.g., 120 Volts (V) alternating current at 60 Hertz in theUnited States). Power source 1130 can include one or more transformers,rectifiers, etc. to convert electrical power into power usable by theone or more elements of controller 1100, such as 1.5 V, 8 V, 12 V, 24 V,etc. Power source 1130 can include one or more batteries.

In some embodiments, controller 1100 can include user interface 1125.User interface 1125 can be configured to receive and/or provideinformation from/to a user, such as a system administrator, a buyer, asupplier, etc. User interface 1125 can be any user interface known inthe art. User interface 1125 can be an interface for receiving userinput and/or machine instructions for entry into controller 1100 usingany suitable method. User interface 1125 may use various inputtechnologies including, but not limited to, a keyboard, a stylus and/ortouch screen, a mouse, a track ball, a keypad, a microphone, voicerecognition, motion recognition, disk drives, remote controllers, inputports, one or more buttons, dials, joysticks, etc. to allow an externalsource, such as a user, to enter information into controller 1100. Userinterface 1125 can be used to navigate menus, adjust options, adjustsettings, adjust display, etc. User interface 1125 can be configured toprovide an interface for presenting information from controller 1100 toexternal systems, users, or memory. For example, user interface 1125 caninclude an interface for a display, a printer, a speaker,alarm/indicator lights, a network interface, a disk drive, a computermemory device, etc. User interface 1125 can include a color display, acathode-ray tube (CRT), a liquid crystal display (LCD), a plasmadisplay, an organic light-emitting diode (OLED) display, etc.

The operations described in this specification can be implemented asoperations performed by a data processing apparatus on data stored onone or more computer-readable storage devices or received from othersources. The term “data processing apparatus” or “computing device”encompasses all kinds of apparatus, devices, and machines for processingdata, including by way of example a programmable processor, a computer,a system on a chip, or multiple ones, or combinations, of the foregoing.The apparatus can include special purpose logic circuitry, e.g., an FPGA(field programmable gate array) or an ASIC (application-specificintegrated circuit). The apparatus can also include, in addition tohardware, code that creates an execution environment for the computerprogram in question, e.g., code that constitutes processor firmware, aprotocol stack, a database management system, an operating system, across-platform runtime environment, a virtual machine, or a combinationof one or more of them. The apparatus and execution environment canrealize various different computing model infrastructures, such as webservices, distributed computing and grid computing infrastructures.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, declarative orprocedural languages, and it can be deployed in any form, including as astand-alone program or as a module, component, subroutine, object, orother unit suitable for use in a computing environment. A computerprogram may, but need not, correspond to a file in a file system. Aprogram can be stored in a portion of a file that holds other programsor data (e.g., one or more scripts stored in a markup languagedocument), in a single file dedicated to the program in question, or inmultiple coordinated files (e.g., files that store one or more modules,sub-programs, or portions of code). A computer program can be deployedto be executed on one computer or on multiple computers that are locatedat one site or distributed across multiple sites and interconnected by acommunication network.

The processes and logic flows described in this specification can beperformed by one or more programmable processors executing one or morecomputer programs to perform actions by operating on input data andgenerating output. The processes and logic flows can also be performedby, and apparatus can also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application-specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read-only memory ora random access memory or both. The essential elements of a computer area processor for performing actions in accordance with instructions andone or more memory devices for storing instructions and data. Generally,a computer will also include, or be operatively coupled to receive datafrom or transfer data to, or both, one or more mass storage devices forstoring data, e.g., magnetic, magneto-optical disks, or optical disks.However, a computer need not have such devices. Moreover, a computer canbe embedded in another device, e.g., a mobile telephone, a personaldigital assistant (PDA), a mobile audio or video player, a game console,a Global Positioning System (GPS) receiver, or a portable storage device(e.g., a universal serial bus (USB) flash drive), to name just a few.Devices suitable for storing computer program instructions and datainclude all forms of non-volatile memory, media and memory devices,including by way of example semiconductor memory devices, e.g., EPROM,EEPROM, and flash memory devices; magnetic disks, e.g., internal harddisks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROMdisks. The processor and the memory can be supplemented by, orincorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subjectmatter described in this specification can be implemented on a computerhaving a display device, e.g., a CRT (cathode ray tube) or LCD (liquidcrystal display) monitor, for displaying information to the user and akeyboard and an I/O device, e.g., a mouse or a touch sensitive screen,by which the user can provide input to the computer. Other kinds ofdevices can be used to provide for interaction with a user as well; forexample, feedback provided to the user can be any form of sensoryfeedback, e.g., visual feedback, auditory feedback, or tactile feedback;and input from the user can be received in any form, including acoustic,speech, or tactile input. In addition, a computer can interact with auser by sending documents to and receiving documents from a device thatis used by the user; for example, by sending web pages to a web browseron a user's client device in response to requests received from the webbrowser.

Embodiments of the subject matter described in this specification can beimplemented in a computing system that includes a back-end component,e.g., as a data server, or that includes a middleware component, e.g.,an application server, or that includes a front-end component, e.g., aclient computer having a graphical user interface or a web browserthrough which a user can interact with an implementation of the subjectmatter described in this specification, or any combination of one ormore such back-end, middleware, or front-end components. The componentsof the system can be interconnected by any form or medium of digitaldata communication, e.g., a communication network. Examples ofcommunication networks include a local area network (“LAN”) and a widearea network (“WAN”), an inter-network (e.g., the Internet), andpeer-to-peer networks (e.g., ad hoc peer-to-peer networks).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someembodiments, a server transmits data (e.g., an HTML page) to a clientdevice (e.g., for purposes of displaying data to and receiving userinput from a user interacting with the client device). Data generated atthe client device (e.g., a result of the user interaction) can bereceived from the client device at the server.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as descriptions offeatures specific to particular embodiments of particular inventions.Certain features that are described in this specification in the contextof separate embodiments can also be implemented in combination in asingle embodiment. Conversely, various features that are described inthe context of a single embodiment can also be implemented in multipleembodiments separately or in any suitable sub-combination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

Thus, particular embodiments of the subject matter have been described.In some cases, the actions recited herein can be performed in adifferent order and still achieve desirable results. In addition, theprocesses depicted in the accompanying figures do not necessarilyrequire the particular order shown, or sequential order, to achievedesirable results. In certain implementations, multitasking and parallelprocessing may be advantageous.

What is claimed is:
 1. A method for managing a supply chain comprising:monitoring, by a computing system, a plurality of computerized resourcesfor information related to supply chain disruption events; predicting,by the computing system, a geographic location affected by a supplychain disruption event based on the information related to supply chaindisruption events; determining, by the computing system, a supplieraffected by the supply chain disruption event at the geographiclocation, wherein determining the supplier affected by the supply chaindisruption event comprises comparing a geographic location affected bythe supply chain disruption event to a location of the supplier, andwherein the supplier is responsible for providing a product thatsatisfies a criterion of a buyer; determining, by the computing system,a risk level associated with the supplier in accordance with the supplychain disruption event at the geographic location, wherein determiningthe risk level comprises comparing a risk value associated with thesupplier to one or more risk tolerance thresholds; monitoring, by thecomputing system, the supply chain disruption event over time; updating,by the computing system, the risk level associated with the supplierbased on the monitoring of the supply chain disruption event; andproviding, by the computing system, one or more updates regarding therisk level associated with the supplier.
 2. The method of claim 1,further comprising: flagging the supplier within a database of potentialsuppliers in response to determining that the risk value is greater thanthe risk tolerance threshold; and notifying the buyer that the supplierhas been flagged, wherein said notifying the buyer comprises indicatingto the buyer that the first supplier is at risk of failing to deliverthe first product to the buyer before a previously agreed-upon deliverydate.
 3. The method of claim 1, wherein predicting the geographiclocation affected by the supply chain disruption event comprisescomparing a number of the computerized sources providing informationindicative of the supply chain disruption event to a threshold number ofsources, and wherein the geographic location is predicted to be affectedby the supply chain disruption event in response to the number of thecomputerized sources satisfying the threshold number of sources.
 4. Themethod of claim 3, wherein the threshold number of sources is dependenton the reliability of the computerized sources.
 5. The method of claim1, wherein predicting the geographic location affected by the supplychain disruption event comprises: weighting each computerized source;aggregating weights of the computerized sources providing informationindicative of the supply chain disruption event; and comparing theaggregated weights of the computerized sources to a threshold score, andwherein the geographic location is predicted to be affected by thesupply chain disruption event in response to the aggregated weightssatisfying the threshold score.
 6. The method of claim 5, wherein atleast one of the weights of the computerized sources include a timedecay element such that the weight is adjusted based on an amount oftime since reporting of the information indicative of the supply chaindisruption event by a respective computerized source.
 7. The method ofclaim 5, further comprising adjusting the aggregated weights based on abusiness category of the supplier.
 8. The method of claim 1, furthercomprising: predicting, by the computing system, one or more suppliersaffected by a non-location specific supply chain disruption event basedon the information related to supply chain disruption events;determining, by the computing system, a risk level associated with theone or more suppliers affected by the non-location specific supply chaindisruption event; monitoring, by the computing system, the non-locationspecific supply chain disruption event over time; updating, by thecomputing system, the risk level associated with the one or moresuppliers affected by non-location specific supply chain disruptionevent based on the monitoring of the non-location specific supply chaindisruption event; and providing, by the computing system, one or moreupdates regarding the risk level associated with the one or moresuppliers affected by non-location specific supply chain disruptionevent.
 9. The method of claim 1, further comprising searching, by thecomputing system, the information related to supply chain disruptionevents for keywords that are indicative that a supply chain disruptionevent has occurred.
 10. The method of claim 1, further comprisingproviding a list of recommended suppliers to the buyer, wherein therecommended suppliers are each capable of providing a respective secondproduct to the buyer, wherein the respective second product satisfiesthe criterion of the buyer.
 11. The method of claim 10, furthercomprising: receiving buyer preference information; receivingbuyer-supplier association information that indicates relationshipsbetween the buyer and one or more of the potential suppliers; receivingtransportation cost information that indicates transportation costs ofthe respective second products from locations of the potential suppliersand a location of the buyer; and determining the list of recommendedsuppliers based on the information, the buyer preference information,the buyer-supplier association information, and the transportation costinformation, wherein the list of recommended suppliers comprises atleast one supplier of the potential suppliers.
 12. The method of claim10, further comprising displaying, on a graphical display device, thelist of recommended suppliers in an order based on an aggregate scorefor each of the recommended suppliers.
 13. A system for managing asupply chain comprising: a communications transceiver configured tocommunicate with a plurality of buyers and a plurality of suppliers; amemory configured to store disruption event information and supplierinformation, wherein the supplier information relates to operations of asupplier and includes a location of the supplier, wherein the supplieris responsible for providing a first product that satisfies criteria ofa buyer, and wherein the disruption event information comprisesinformation indicating a supply chain disruption event; and a processoroperatively coupled to the communications transceiver and the memory,wherein the processor is configured to: monitor a plurality ofcomputerized resources for the disruption event information; predict ageographic location affected by a supply chain disruption event based onthe disruption event information; determine the supplier is affected bythe supply chain disruption event at the geographic location, whereindetermining the supplier is affected by the supply chain disruptionevent comprises comparing a geographic location affected by the supplychain disruption event to the location of the supplier; determine a risklevel associated with the supplier in accordance with the supply chaindisruption event at the geographic location, wherein determining therisk level comprises comparing a risk value associated with the supplierto one or more risk tolerance thresholds; monitor the supply chaindisruption event over time; update the risk level associated with thesupplier based on the monitoring of the supply chain disruption event;and provide one or more updates regarding the risk level associated withthe supplier.
 14. The system of claim 13, wherein the processor isfurther configured to: flag the supplier within a database of potentialsuppliers in response to determining that the risk value is greater thanthe risk tolerance threshold; and notify the buyer that the supplier hasbeen flagged, wherein said notifying the buyer comprises indicating tothe buyer that the first supplier is at risk of failing to deliver thefirst product to the buyer before a previously agreed-upon deliverydate.
 15. The system of claim 13, wherein predicting the geographiclocation affected by the supply chain disruption event comprisescomparing a number of the computerized sources providing informationindicative of the supply chain disruption event to a threshold number ofsources, and wherein the geographic location is predicted to be affectedby the supply chain disruption event in response to the number of thecomputerized sources satisfying the threshold number of sources.
 16. Thesystem of claim 15, wherein the threshold number of sources is dependenton the reliability of the computerized sources.
 17. The system of claim13, wherein, to predict the geographic location affected by the supplychain disruption event, the processor is configured to: weight eachcomputerized source; aggregate weights of the computerized sourcesproviding information indicative of the supply chain disruption event;and compare the aggregated weights of the computerized sources to athreshold score, and wherein the geographic location is predicted to beaffected by the supply chain disruption event in response to theaggregated weights satisfying the threshold score.
 18. The system ofclaim 17, wherein at least one of the weights of the computerizedsources include a time decay element such that the weight is adjustedbased on an amount of time since reporting of the information indicativeof the supply chain disruption event by a respective computerizedsource.
 19. The system of claim 17, further comprising adjusting theaggregated weights based on a business category of the supplier.
 20. Anon-transitory computer-readable medium including computer-readableinstructions that, upon execution by a processor, cause a device to:monitor a plurality of computerized resources for information related tosupply chain disruption events; predict a geographic location affectedby a supply chain disruption event based on the information related tosupply chain disruption events; determine a supplier affected by thesupply chain disruption event at the geographic location, whereindetermining the supplier affected by the supply chain disruption eventcomprises comparing a geographic location affected by the supply chaindisruption event to a location of the supplier, and wherein the supplieris responsible for providing a product that satisfies a criterion of abuyer; determine a risk level associated with the supplier in accordancewith the supply chain disruption event at the geographic location,wherein determining the risk level comprises comparing a risk valueassociated with the supplier to one or more risk tolerance thresholds;monitor the supply chain disruption event over time; update the risklevel associated with the supplier based on the monitoring of the supplychain disruption event; and provide one or more updates regarding therisk level associated with the supplier.